Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WqTWN-0000oC-23 for pgsql-bugs@arkaria.postgresql.org; Fri, 30 May 2014 20:35:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WqTWM-0008Nj-9D for pgsql-bugs@arkaria.postgresql.org; Fri, 30 May 2014 20:35:22 +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 1WqTWL-0008KI-0S for pgsql-bugs@postgresql.org; Fri, 30 May 2014 20:35:21 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1WqTWH-0002jG-I4 for pgsql-bugs@postgresql.org; Fri, 30 May 2014 20:35:19 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1WqTWF-0001IU-Io; Fri, 30 May 2014 16:35:15 -0400 Date: Fri, 30 May 2014 16:35:15 -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: <20140530203515.GS28490@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140530151317.GB1220@awork2.anarazel.de> 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:13:17PM +0200, Andres Freund wrote: > On 2014-05-30 11:00:06 -0400, Bruce Momjian wrote: > > On Fri, May 30, 2014 at 03:32:44PM +0200, Andres Freund wrote: > > > On 2014-05-30 09:29:16 -0400, Bruce Momjian wrote: > > > > This is a bug in 9.3 pg_upgrade as well? > > > > > > Yes. > > > > > > > Why has no one reported it before? > > > > > > My guess is that it wasn't attributed to pg_upgrade in the > > > past. Typically the error will only occur a fair amount of time > > > later. You'll just see vacuums randomly erroring out with slru.c errors > > > about nonexistant files :(. > > > > But how much later? pg_upgrade is pretty popular now but I am just not > > seeing the number of errors as I would expect: > > > > ERROR: could not access status of transaction 2072053907 > > DETAIL: Could not open file "pg_multixact/offsets/7B81": No such file or directory. > > > I am not saying there is no bug, but from your analysis it would seem to > > be 100% of pg_upgrade'ed clusters that use multi-xacts. > > 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? Multi-xacts were added in 9.3: commit 0ac5ad5134f2769ccbaefec73844f8504c4d6182 Author: Alvaro Herrera Date: Wed Jan 23 12:04:59 2013 -0300 Improve concurrency of foreign key locking -- 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