From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |
Date: | 2014-06-20 01:06:54 |
Message-ID: | 20140620010653.GS18688@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-06-20 10:11:05 | Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process |
Previous Message | Andres Freund | 2014-06-19 23:59:57 | Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process |