On 8 March 2018 at 16:55, Amit Khandekar <amitdkhan...@gmail.com> wrote: > The attached WIP patch is how the fix is turning out to be. > ExecDelete() passes back the epqslot returned by EvalPlanQual(). > ExecUpdate() uses this re-fetched tuple to re-process the row, just > like it does when heap_update() returns HeapTupleUpdated. > > I need to write an isolation test for this fix.
Attached patch now has the isolation test included. The only difference with the earlier WIP patch is about some cosmetic changes, and some more comments. > > [1] : > https://www.postgresql.org/message-id/CAJ3gD9d%3DwcbF-G00bYo4v5iWC69zm1UTSNxyRLpOgO9j4AtLWQ%40mail.gmail.com > > > -- > Thanks, > -Amit Khandekar > EnterpriseDB Corporation > The Postgres Database Company -- Thanks, -Amit Khandekar EnterpriseDB Corporation The Postgres Database Company
fix_concurrency_bug.patch
Description: Binary data
