| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Olivier Dony <odo+pgbugs(at)odoo(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Olivier Dony <odo(at)odoo(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13681: Serialization failures caused by new multixact code of 9.3 (back-patch request) |
| Date: | 2016-07-15 18:23:13 |
| Message-ID: | 20160715182313.GA157635@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles | 2016-07-15 18:48:21 | Using row-level security results in less optimal query plans |
| Previous Message | Teodor Sigaev | 2016-07-15 16:27:23 | Re: BUG #14245: Segfault on weird to_tsquery |