Date: Wed, 8 Oct 2014 14:26:46 -0700 (PDT)
From: jim_yates <pg@wg5jim.net>
To: pgsql-sql@postgresql.org
Message-ID: <1412803606495-5822295.post@n5.nabble.com>
In-Reply-To: <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>
 <20141008205416.GZ7043@eldon.alvh.no-ip.org>
Subject: Re: could not access status of transaction pg_multixact issue
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Alvaro Herrera-9 wrote
> The one labelled NextMultiXactId.
>=20
>> I also assume I would do the pg_database update on a idle database.
>=20
> It doesn't matter, actually.  pg_database is a shared catalog, so an
> update would affect all the databases.
>=20
> --=20
> =C3=81lvaro 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.=20=20=20

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.


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