Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ws6wl-0003vu-UY for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Jun 2014 08:53:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Ws6wl-0004II-E0 for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Jun 2014 08:53:23 +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 1Ws6wk-0004IB-HO for pgsql-bugs@postgresql.org; Wed, 04 Jun 2014 08:53:22 +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 1Ws6wf-0000w3-V1 for pgsql-bugs@postgresql.org; Wed, 04 Jun 2014 08:53:21 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1Ws6wc-0005n7-Sp; Wed, 04 Jun 2014 04:53:14 -0400 Date: Wed, 4 Jun 2014 04:53:14 -0400 From: Bruce Momjian To: Andres Freund Cc: PostgreSQL Bugs , Alvaro Herrera Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts Message-ID: <20140604085314.GA19423@momjian.us> References: <20140530121631.GE25431@alap3.anarazel.de> <20140530132916.GM28490@momjian.us> <20140530133244.GG25431@alap3.anarazel.de> <20140530150006.GP28490@momjian.us> <20140530151317.GB1220@awork2.anarazel.de> <20140530203515.GS28490@momjian.us> <20140530210353.GI30516@awork2.anarazel.de> <20140530212526.GT28490@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140530212526.GT28490@momjian.us> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -2.6 (--) 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 Fri, May 30, 2014 at 05:25:26PM -0400, Bruce Momjian wrote: > On Fri, May 30, 2014 at 11:03:53PM +0200, Andres Freund wrote: > > On 2014-05-30 16:35:15 -0400, Bruce Momjian wrote: > > > On Fri, May 30, 2014 at 05:13:17PM +0200, Andres Freund wrote: > > > > It'd need to be clusters that used more multixacts than fit onto two > > > > slru offsets/ segments in < 9.2. Otherwise things will probably just > > > > continue to work because there's no hole. > > > > > > Do you mean <= 9.2 here for the old cluster? > > > > yes. > > > > > Multi-xacts were added in 9.3: > > > > That's not really correct. They were added in 8.2 or something... > > > > > commit 0ac5ad5134f2769ccbaefec73844f8504c4d6182 > > > Author: Alvaro Herrera > > > Date: Wed Jan 23 12:04:59 2013 -0300 > > > > > > Improve concurrency of foreign key locking > > > > That just expanded the usage to also be able to track updated rows. > > I guess I meant the new multixacts file format was in 9.3. It appears this item is on hold until Alvaro can comment. I can probably find the impact and correct the problem for previous upgrades, but it might be 1-2 months until I can get to it. The fix for future upgrades is simple. -- 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