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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()
Date: 2023-04-05 02:54:06
Message-ID: ZCzizp7mNQ52W3Qn@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 04, 2023 at 01:25:46AM +0300, Alexander Korotkov wrote:
> Pavel, thank you for you review, revisions and rebase.
> We'll reconsider this once v17 is branched.

The patch was still in the current CF, so I have moved it to the next
one based on the latest updates.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-05 03:14:17 Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode
Previous Message Michael Paquier 2023-04-05 02:48:51 Re: [BUG] pg_stat_statements and extended query protocol