From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Olivier Dony <odo+pgbugs@odoo.com>
Cc: Kevin Grittner <kgrittn@gmail.com>
Cc: Olivier Dony <odo@odoo.com>
Cc: 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)
Date: Tue, 5 Jul 2016 18:00:31 -0400
Message-ID: <20160705220031.GA602524@alvherre.pgsql> (raw)
In-Reply-To: <CAP4GjTKdFn4MF+GndusWWxOJNF2aQ=DYrPYoNRytEKkm2twUZg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachments:
0001-test-cases.patch (text/x-diff, 0B) 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-bugs@postgresql.org
Cc: alvherre@2ndquadrant.com, odo+pgbugs@odoo.com, kgrittn@gmail.com, odo@odoo.com
Subject: Re: BUG #13681: Serialization failures caused by new multixact code of 9.3 (back-patch request)
In-Reply-To: <20160705220031.GA602524@alvherre.pgsql>
* 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