Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X909t-0002rd-Nm for pgsql-bugs@arkaria.postgresql.org; Sun, 20 Jul 2014 23:04:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X909t-0004gA-4M for pgsql-bugs@arkaria.postgresql.org; Sun, 20 Jul 2014 23:04:45 +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 1X909s-0004g3-0r for pgsql-bugs@postgresql.org; Sun, 20 Jul 2014 23:04:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X909o-00059I-J9 for pgsql-bugs@postgresql.org; Sun, 20 Jul 2014 23:04:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s6KN4URp018674; Sun, 20 Jul 2014 19:04:30 -0400 From: Tom Lane To: Andres Freund cc: Bruce Momjian , Alvaro Herrera , PostgreSQL Bugs Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts In-reply-to: <20140720225653.GG5974@alap3.anarazel.de> References: <20140720200225.GA5974@alap3.anarazel.de> <13755.1405887378@sss.pgh.pa.us> <20140720204852.GB5974@alap3.anarazel.de> <15685.1405891368@sss.pgh.pa.us> <20140720213258.GD5974@alap3.anarazel.de> <16274.1405892584@sss.pgh.pa.us> <20140720220253.GE5974@alap3.anarazel.de> <17255.1405894611@sss.pgh.pa.us> <20140720223010.GF5974@alap3.anarazel.de> <17935.1405895946@sss.pgh.pa.us> <20140720225653.GG5974@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 21 Jul 2014 00:56:53 +0200" Date: Sun, 20 Jul 2014 19:04:30 -0400 Message-ID: <18673.1405897470@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org Andres Freund writes: > If any *single* full table vacuum after that calls > vac_update_datfrozenxid() which just needs its datfrozenxid advance by > one we're in trouble: vac_truncate_clog() will be called with minMulti = > GetOldestMultiXactId(). Uh, no, the cutoff is GetOldestMultiXactId minus vacuum_multixact_freeze_min_age (or the autovac equivalent). See vacuum_set_xid_limits. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs