Horton

Re: POC: Lock updated tuples in tuple_update() and tuple_delete()

Gregory Stark <stark@postgresql.org>

View thread View on postgr.es
From: Gregory Stark <stark@postgresql.org>
To: Andres Freund <andres@anarazel.de>
Cc: Alexander Korotkov <aekorotkov@gmail.com>, Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Mason Sharp <masonlists@gmail.com>, Pavel Borisov <pashkin.elfe@gmail.com>, vignesh C <vignesh21@gmail.com>
Date: 2023-02-28T21:02:46Z
Lists: pgsql-hackers 
It looks like this patch received some feedback from Andres and hasn't
had any further work posted. I'm going to move it to "Waiting on
Author".

It doesn't sound like this is likely to get committed this release
cycle unless responding to Andres's points simpler than I expect.

Commits

  1. Add EvalPlanQual delete returning isolation test

  2. Allow locking updated tuples in tuple_update() and tuple_delete()

  3. Revert 764da7710b

  4. Revert 11470f544e

  5. Evade extra table_tuple_fetch_row_version() in ExecUpdate()/ExecDelete()

  6. Check that xmax didn't commit in freeze check.