Re: could not access status of transaction pg_multixact issue - Mailing list pgsql-sql

From Alvaro Herrera
Subject Re: could not access status of transaction pg_multixact issue
Date
Msg-id 20141008205416.GZ7043@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: could not access status of transaction pg_multixact issue  (jim_yates <pg@wg5jim.net>)
Responses Re: could not access status of transaction pg_multixact issue
Re: could not access status of transaction pg_multixact issue
List 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 by date:

Previous
From: jim_yates
Date:
Subject: Re: could not access status of transaction pg_multixact issue
Next
From: jim_yates
Date:
Subject: Re: could not access status of transaction pg_multixact issue