| From: | jim_yates <pg(at)wg5jim(dot)net> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: could not access status of transaction pg_multixact issue |
| Date: | 2014-10-08 21:26:46 |
| Message-ID: | 1412803606495-5822295.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Alvaro Herrera-9 wrote
> 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
Right now my Latest checkpoint's NextMultiXactId is 302870
and the relminmxid from pg_class for the table in question is 1.
So I would set the pg_database.datxminmxid to 302869.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-pg-multixact-issue-tp5822248p5822295.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jim_yates | 2014-10-09 14:07:00 | Re: could not access status of transaction pg_multixact issue |
| Previous Message | Alvaro Herrera | 2014-10-08 20:54:16 | Re: could not access status of transaction pg_multixact issue |