| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Need Multixact Freezing Docs |
| Date: | 2014-08-28 16:09:45 |
| Message-ID: | 20140828160945.GQ7046@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
> On 04/16/2014 01:30 PM, Alvaro Herrera wrote:
> > Josh Berkus wrote:
> >>
> >>> You can see the current multixact value in pg_controldata output. Keep
> >>> timestamped values of that somewhere (a table?) so that you can measure
> >>> consumption rate. I don't think we provide SQL-level access to those
> >>> values.
> >>
> >> Bleh. Do we provide SQL-level access in 9.4? If not, I think that's a
> >> requirement before release.
> >
> > Yeah, good idea. Want to propose a patch?
>
> Yeah, lemme dig into this. I really think we need it for 9.4, feature
> frozen or not.
Ping?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-08-28 16:18:34 | Re: Per table autovacuum vacuum cost limit behaviour strange |
| Previous Message | Claudio Freire | 2014-08-28 16:00:02 | Re: postgresql latency & bgwriter not doing its job |