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

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Pavel Borisov <pashkin.elfe@gmail.com>, Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Mason Sharp <masonlists@gmail.com>, vignesh C <vignesh21@gmail.com>

Date: 2023-01-09T23:38:58Z

Lists: pgsql-hackers

Hi,

On 2023-01-09 13:46:50 +0300, Alexander Korotkov wrote:
> I'm going to push v9.

Could you hold off for a bit? I'd like to look at this, I'm not sure I like
the direction.

Greetings,

Andres Freund

Commits

Add EvalPlanQual delete returning isolation test
- 8ffc2aa720a2 17.0 landed
Allow locking updated tuples in tuple_update() and tuple_delete()
- 87985cc92522 17.0 landed
- 11470f544e37 16.0 landed
Revert 764da7710b
- b0b91ced167f 16.0 landed
Revert 11470f544e
- 2b65bf046d8a 16.0 landed
Evade extra table_tuple_fetch_row_version() in ExecUpdate()/ExecDelete()
- 764da7710bf6 16.0 landed
Check that xmax didn't commit in freeze check.
- eb5ad4ff05fd 16.0 cited