pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date: Thu, 19 Jun 2014 21:06:54 -0400
Message-ID: <20140620010653.GS18688@eldon.alvh.no-ip.org> (raw)
In-Reply-To: <20140619220425.GQ18688@eldon.alvh.no-ip.org>
References: <20140619020633.GA20469@momjian.us>
	<20140619015205.GD3806@momjian.us>
	<20140619014034.GC3806@momjian.us>
	<20140619220425.GQ18688@eldon.alvh.no-ip.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>

Alvaro Herrera wrote:
> Bruce Momjian wrote:

> Bruce Momjian wrote:
> 
> > > OK, so the xid has to be beyond 2^31 during pg_upgrade to trigger a
> > > problem?  That might explain the rare reporting of this bug.  What would
> > > the test query look like so we can tell people when to remove the '0000'
> > > files?  Would we need to see the existence of '0000' and high-numbered
> > > files?  How high?  What does a 2^31 file look like?
> > 
> > Also, what would a legitimate 0000 file at wrap-around time look like?
> > Would there have to be an 'ffff' or 'ffffff' file?
> 
> Since I was wrong, there is no point in further research here.  Anyway
> the last file before wrapping around in pg_multixact/members is FFFF.

Oops, I meant the last file before wrap in pg_multixact/offsets is FFFF,
which is what we're talking about in this thread.

For members it's 14078, but it's not relevant here.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


-- 
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: <20140620010653.GS18688@eldon.alvh.no-ip.org>
Permalink:  ../20140620010653.GS18688@eldon.alvh.no-ip.org/
Also on:    postgresql.org/message-id/20140620010653.GS18688@eldon.alvh.no-ip.org

 · 

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: alvherre@2ndquadrant.com, bruce@momjian.us, andres@2ndquadrant.com
  Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
  In-Reply-To: <20140620010653.GS18688@eldon.alvh.no-ip.org>

* 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