Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X9ZpA-0005OD-Fn for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Jul 2014 13:09:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X9Zp9-0002NF-Iw for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Jul 2014 13:09:43 +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 1X9Zp8-0002N9-Te for pgsql-bugs@postgresql.org; Tue, 22 Jul 2014 13:09:42 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X9Zp1-0005kJ-Ec for pgsql-bugs@postgresql.org; Tue, 22 Jul 2014 13:09:41 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1X9Zox-0001vq-7Q; Tue, 22 Jul 2014 09:09:31 -0400 Date: Tue, 22 Jul 2014 09:09:31 -0400 From: Bruce Momjian To: Tom Lane Cc: Andres Freund , Alvaro Herrera , PostgreSQL Bugs Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts Message-ID: <20140722130931.GA1563@momjian.us> References: <20140720223010.GF5974@alap3.anarazel.de> <17935.1405895946@sss.pgh.pa.us> <20140720225653.GG5974@alap3.anarazel.de> <18673.1405897470@sss.pgh.pa.us> <18851.1405897900@sss.pgh.pa.us> <20140720233125.GI5974@alap3.anarazel.de> <19458.1405899435@sss.pgh.pa.us> <20140720234925.GJ5974@alap3.anarazel.de> <22178.1405903964@sss.pgh.pa.us> <26504.1405912770@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26504.1405912770@sss.pgh.pa.us> User-Agent: Mutt/1.5.20 (2009-06-14) 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 On Sun, Jul 20, 2014 at 11:19:30PM -0400, Tom Lane wrote: > I wrote: > > Here's a draft patch for this. I think this will fix all cases where > > the "1" minmxid inserted by previous pg_upgrade versions is actually > > in the future at the time we run VACUUM. We would still be at risk if > > it had been in the future when pg_upgrade ran but no longer is now, > > since that would mean there could be non-lock-only mxids on disk that > > are older than "1". However, for the reasons discussed upthread, it > > seems fairly unlikely to me that people would actually get burnt in > > practice, so I'm satisfied with doing this much and no more. > > Ah, belay that: as coded, that would allow truncation of clog/multixact > as soon as any one relation in any one database had sane > frozenxid/minmxid. If we want to have any pretense of being safe, we have > to postpone truncation until *all* relations have been vacuumed. So more > like the attached, instead. Should we conclude that the multi-xact code is hopelessly complex and needs a redesign? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs