Re: could not access status of transaction pg_multixact issue

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: jim_yates <pg(at)wg5jim(dot)net>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: could not access status of transaction pg_multixact issue
Date: 2014-10-08 20:54:16
Message-ID: 20141008205416.GZ7043@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message jim_yates 2014-10-08 21:26:46 Re: could not access status of transaction pg_multixact issue
Previous Message jim_yates 2014-10-08 19:43:35 Re: could not access status of transaction pg_multixact issue