Re: Need Multixact Freezing Docs
Josh Berkus <josh@agliodbs.com>
From: Josh Berkus <josh@agliodbs.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2014-04-16T18:06:19Z
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
Commits
-
Document pg_get_multixact_members().
- f5551538bce0 17.6 landed
- e6115394d40c 19 (unreleased) landed
- e35a0174a9d2 14.19 landed
- d271b04dc64e 16.10 landed
- c8b9f75111aa 18.0 landed
- a167e654d06f 15.14 landed
- 0ee7f51a8b4e 13.22 landed