pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date: Fri, 30 May 2014 16:35:15 -0400
Message-ID: <20140530203515.GS28490@momjian.us> (raw)
In-Reply-To: <20140530151317.GB1220@awork2.anarazel.de>
References: <20140530121631.GE25431@alap3.anarazel.de>
	<20140530132916.GM28490@momjian.us>
	<20140530133244.GG25431@alap3.anarazel.de>
	<20140530150006.GP28490@momjian.us>
	<20140530151317.GB1220@awork2.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>

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 <alvherre@alvh.no-ip.org>
        Date:   Wed Jan 23 12:04:59 2013 -0300

            Improve concurrency of foreign key locking

-- 
  Bruce Momjian  <bruce@momjian.us>        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



view thread (78+ messages)  latest in thread

Message-ID: <20140530203515.GS28490@momjian.us>
Permalink:  ../20140530203515.GS28490@momjian.us/
Also on:    postgresql.org/message-id/20140530203515.GS28490@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: bruce@momjian.us, andres@2ndquadrant.com, alvherre@2ndquadrant.com
  Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
  In-Reply-To: <20140530203515.GS28490@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox