Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XcK9A-0002BS-NA for pgsql-sql@arkaria.postgresql.org; Thu, 09 Oct 2014 20:17:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XcK9A-0008Hj-6H for pgsql-sql@arkaria.postgresql.org; Thu, 09 Oct 2014 20:17:12 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XcK98-0008Ex-PZ for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 20:17:10 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XcK95-0005Wf-Co for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 20:17:08 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XcK94-0000IC-Bf for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 13:17:06 -0700 Date: Thu, 9 Oct 2014 13:17:06 -0700 (PDT) From: jim_yates To: pgsql-sql@postgresql.org Message-ID: <1412885826355-5822449.post@n5.nabble.com> In-Reply-To: <20141009180022.GE7043@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> <1412863620263-5822376.post@n5.nabble.com> <5436A34C.8090306@aklaver.com> <20141009151229.GD7043@eldon.alvh.no-ip.org> <1412874160409-5822399.post@n5.nabble.com> <20141009180022.GE7043@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 X-Pg-Spam-Score: -0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Alvaro Herrera-9 wrote > You need to *minimum* of all the values in relminmxid (excluding those > that are zero). >=20 > The pg_controldata value is a mechanism to determine which value is > minimum -- when there's been wraparound, the minimum might be "smaller > than zero", i.e. something like 4 thousand millions. I doubt this is > your case though. >=20 > --=20 > =C3=81lvaro Herrera http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services Then I'm really confused.=20=20 The minimum relminmxid for all the rows in pg_class that have relminmxid greater then zero is 1. That's the current value of datminmxid in pg_database.=20=20 And the NextMultiXactId from pg_controldump is 303464. So if I use the min value from pg_class then I have some other issue.=20=20 Where should I get the new pg_database value from? -- View this message in context: http://postgresql.1045698.n5.nabble.com/could= -not-access-status-of-transaction-pg-multixact-issue-tp5822248p5822449.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