Date: Fri, 15 Jul 2016 14:23:13 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Olivier Dony <odo+pgbugs@odoo.com>
Cc: Kevin Grittner <kgrittn@gmail.com>, Olivier Dony <odo@odoo.com>,
	"pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>
Subject: Re: BUG #13681: Serialization failures caused by new
 multixact code of 9.3 (back-patch request)
Message-ID: <20160715182313.GA157635@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20160705220031.GA602524@alvherre.pgsql>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

Alvaro Herrera wrote:
> I'm looking at this open bug again.  I attach two commits; the first one
> adds two test cases illustrating the current (broken) behavior, and the
> second one adds the fix and changes the test cases to match the new
> behavior.  I spent a lot of time trying to find (a) any other
> HeapTupleSatisfiesUpdate caller that needed to be changed, and (b)
> additional test cases that showed misbehavior, and so far I haven't been
> able to come up with any.
> 
> No other test case is affected AFAICS.
> 
> I intend to push this and backpatch to 9.3.

Pushed.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, 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