From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Need Multixact Freezing Docs |
Date: | 2014-04-16 18:06:19 |
Message-ID: | 534EC69B.9010107@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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. Telling users to monitor a setting using a
restricted-permission command-line utility which produces a
version-specific text file they have to parse is not going to win us a
lot of fans.
>
>> Also: how do I check the multixact age of a table? There doesn't seem
>> to be any data for this ...
>
> pg_class.relminmxid is the oldest multixact value that might be present
> in a table.
On every database I've tested, age(relminmxid) returns int_max. So this
is apparently broken.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-04-16 18:07:02 | Re: Clock sweep not caching enough B-Tree leaf pages? |
Previous Message | Robert Haas | 2014-04-16 17:56:18 | Re: Clock sweep not caching enough B-Tree leaf pages? |