Re: could not access status of transaction pg_multixact issue
| От | jim_yates |
|---|---|
| Тема | Re: could not access status of transaction pg_multixact issue |
| Дата | |
| Msg-id | 1412874160409-5822399.post@n5.nabble.com обсуждение исходный текст |
| Ответ на | Re: could not access status of transaction pg_multixact issue (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: could not access status of transaction pg_multixact issue
|
| Список | pgsql-sql |
Alvaro Herrera-9 wrote > > There must have been some confusion somewhere; certainly you shouldn't > be subtracting anything. The subtraction was just suggested as a way to > determine the age. The value to update pg_database.datminmxid to is the > oldest one of all the relminmxid in pg_class; so if you have 8376 as the > minimum value there, that's what you set pg_database.datminmxid to. Not > the 21973 value. > > update pg_database set datminmxid='8376' where datname='production-copy'; Ok, I'm still confused. Is the value to use the Max value of relminmxid from pg_class or the value of NextMultiXactId from pg_controldump? Or are these the same thing? -- View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-pg-multixact-issue-tp5822248p5822399.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
В списке pgsql-sql по дате отправления: