From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Gregory Stark <stark(at)postgresql(dot)org> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Mason Sharp <masonlists(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
Subject: | Re: POC: Lock updated tuples in tuple_update() and tuple_delete() |
Date: | 2023-02-28 21:08:58 |
Message-ID: | CAPpHfdsa_QgLG9N8T=C7pUGiwysCNf_G1tWwXw3_hJ1-ztqE_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 1, 2023 at 12:03 AM Gregory Stark <stark(at)postgresql(dot)org> wrote:
> 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".
I'll post the updated version in the next couple of days.
> It doesn't sound like this is likely to get committed this release
> cycle unless responding to Andres's points simpler than I expect.
I wouldn't think ahead that much.
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-02-28 21:59:48 | Making empty Bitmapsets always be NULL |
Previous Message | Gregory Stark | 2023-02-28 21:02:46 | Re: POC: Lock updated tuples in tuple_update() and tuple_delete() |