Re: Need Multixact Freezing Docs
От | Josh Berkus |
---|---|
Тема | Re: Need Multixact Freezing Docs |
Дата | |
Msg-id | 534EC69B.9010107@agliodbs.com обсуждение исходный текст |
Ответ на | Need Multixact Freezing Docs (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Need Multixact Freezing Docs
Re: Need Multixact Freezing Docs |
Список | 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
В списке pgsql-hackers по дате отправления: