Horton

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

Pavel Borisov <pashkin.elfe@gmail.com>

View thread View on postgr.es
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Alexander Korotkov <aekorotkov@gmail.com>, Chris Travers <chris.travers@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-04-01T07:24:09Z
Lists: pgsql-hackers 
Hi, Andres!

On Sat, 1 Apr 2023, 09:21 Andres Freund, <andres@anarazel.de> wrote:

> Given that the in-tree state has been broken for a week, I think it
> probably
> is time to revert the commits that already went in.
>

It seems that although the patch addressing the issues is not a quick fix,
there is a big progress in it already. I propose to see it's status a week
later and if it is not ready then to revert existing. Hope there are no
other patches in the existing branch complained to suffer this.

Kind regards,
Pavel Borisov,
Supabase

>

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.