Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XcH7D-0001rb-KD for pgsql-sql@arkaria.postgresql.org; Thu, 09 Oct 2014 17:02:59 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XcH7D-0007t2-4b for pgsql-sql@arkaria.postgresql.org; Thu, 09 Oct 2014 17:02:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XcH7C-0007sw-GW for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 17:02:58 +0000 Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XcH6x-0006Cu-SV for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 17:02:57 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XcH6u-0006Ib-DQ for pgsql-sql@postgresql.org; Thu, 09 Oct 2014 10:02:40 -0700 Date: Thu, 9 Oct 2014 10:02:40 -0700 (PDT) From: jim_yates To: pgsql-sql@postgresql.org Message-ID: <1412874160409-5822399.post@n5.nabble.com> In-Reply-To: <20141009151229.GD7043@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> Subject: Re: could not access status of transaction pg_multixact issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 > > There must have been some confusion somewhere; certainly you shouldn't > be subtracting anything. The subtraction was just suggested as a way to > determine the age. The value to update pg_database.datminmxid to is the > oldest one of all the relminmxid in pg_class; so if you have 8376 as the > minimum value there, that's what you set pg_database.datminmxid to. Not > the 21973 value. > > update pg_database set datminmxid='8376' where datname='production-copy'; Ok, I'm still confused. Is the value to use the Max value of relminmxid from pg_class or the value of NextMultiXactId from pg_controldump? Or are these the same thing? -- View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-pg-multixact-issue-tp5822248p5822399.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql