From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: MultiXactId error after upgrade to 9.3.4
Date: Mon, 31 Mar 2014 10:34:24 -0400
Message-ID: <20140331143424.GR4582@tamriel.snowman.net> (raw)
In-Reply-To: <20140331142520.GY9567@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>
<20140331142520.GY9567@eldon.alvh.no-ip.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> > 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.
I haven't got any great explanation for that either. I continue to feel
that it's much more likely that it's an xid than a multixid. Is it
possible that it was stamped with a real xmax through some code path
which ignored the IS_MULTI flag? This could have been from as far back
as 9.0-era. On this over-7TB database, only this one tuple had the
issue. I have another set of databases which add up to ~20TB that I'm
currently testing an upgrade from 9.2 to 9.3 on and will certainly let
everyone know if I run into a similar situation there.
On our smallest DB (which we upgraded first) which is much more OLTP
instead of OLAP, we didn't run into this.
This is all on physical gear and we've seen no indications that there
has been any corruption. Hard to rule it out completely, but it seems
pretty unlikely.
Thanks,
Stephen
Attachments:
[application/pgp-signature] signature.asc (835B, ../20140331143424.GR4582@tamriel.snowman.net/2-signature.asc)
download
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: sfrost@snowman.net, alvherre@2ndquadrant.com, andres@2ndquadrant.com
Subject: Re: MultiXactId error after upgrade to 9.3.4
In-Reply-To: <20140331143424.GR4582@tamriel.snowman.net>
* 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