Re: could not access status of transaction pg_multixact issue
От | Alvaro Herrera |
---|---|
Тема | Re: could not access status of transaction pg_multixact issue |
Дата | |
Msg-id | 20141008205416.GZ7043@eldon.alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: could not access status of transaction pg_multixact issue (jim_yates <pg@wg5jim.net>) |
Ответы |
Re: could not access status of transaction pg_multixact issue
Re: could not access status of transaction pg_multixact issue |
Список | pgsql-sql |
jim_yates wrote: > > A better way not involving mxid_age() would be to use pg_controldata to > > extract the current value of the mxid counter, then subtract the current > > relminmxid from that value. > > > It's not clear which lines from pg_controldata to use for updating > pg_database.datminmxid. The one labelled NextMultiXactId. > I also assume I would do the pg_database update on a idle database. It doesn't matter, actually. pg_database is a shared catalog, so an update would affect all the databases. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-sql по дате отправления: