From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: MultiXactId error after upgrade to 9.3.4
Date: Mon, 31 Mar 2014 11:25:20 -0300
Message-ID: <20140331142520.GY9567@eldon.alvh.no-ip.org> (raw)
In-Reply-To: <20140331140245.GX9567@eldon.alvh.no-ip.org>
References: <20140330040029.GY4582@tamriel.snowman.net>
<20140330141135.GA4582@tamriel.snowman.net>
<20140330185349.GD4582@tamriel.snowman.net>
<20140331115452.GT9567@eldon.alvh.no-ip.org>
<20140331115713.GA18358@alap3.anarazel.de>
<20140331140245.GX9567@eldon.alvh.no-ip.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Alvaro Herrera wrote:
> Andres Freund wrote:
> > On 2014-03-31 08:54:53 -0300, Alvaro Herrera wrote:
> > > My conclusion here is that some part of the code is failing to examine
> > > XMAX_INVALID before looking at the value stored in xmax itself. There
> > > ought to be a short-circuit. Fortunately, this bug should be pretty
> > > harmless.
> > >
> > > .. and after looking, I'm fairly sure the bug is in
> > > heap_tuple_needs_freeze.
> >
> > heap_tuple_needs_freeze() isn't *allowed* to look at
> > XMAX_INVALID. Otherwise it could miss freezing something still visible
> > on a standby or after an eventual crash.
>
> I think this rule is wrong. I think the rule ought to be something like
> "if the XMAX_INVALID bit is set, then reset whatever is there if there
> is something; if the bit is not set, proceed as today". Otherwise we
> risk reading garbage, which is what is happening in this case.
Andres asks on IM: How come there is garbage there in the first place?
I have to admit I have no idea.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, andres@2ndquadrant.com, sfrost@snowman.net
Subject: Re: MultiXactId error after upgrade to 9.3.4
In-Reply-To: <20140331142520.GY9567@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