Date: Wed, 8 Oct 2014 17:54:16 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: jim_yates <pg@wg5jim.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: could not access status of transaction pg_multixact issue
Message-ID: <20141008205416.GZ7043@eldon.alvh.no-ip.org>
References: <1412791213607-5822248.post@n5.nabble.com>
 <20141008185538.GY7043@eldon.alvh.no-ip.org>
 <1412797415000-5822268.post@n5.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1412797415000-5822268.post@n5.nabble.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

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


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql