Date: Mon, 31 Mar 2014 13:57:13 +0200
From: Andres Freund <andres@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Stephen Frost <sfrost@snowman.net>, pgsql-hackers@postgresql.org
Subject: Re: MultiXactId error after upgrade to 9.3.4
Message-ID: <20140331115713.GA18358@alap3.anarazel.de>
References: <20140330040029.GY4582@tamriel.snowman.net>
 <20140330141135.GA4582@tamriel.snowman.net>
 <20140330185349.GD4582@tamriel.snowman.net>
 <20140331115452.GT9567@eldon.alvh.no-ip.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140331115452.GT9567@eldon.alvh.no-ip.org>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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.

Greetings,

Andres Freund

-- 
 Andres Freund	                   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