| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | 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-01-09 10:10:56 |
| Message-ID: | CAPpHfdt70hh+Hz3tgoC+0HxN6uNeLoGWRi95jRAY4HKiqBDrjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Aleksander,
On Mon, Jan 9, 2023 at 12:56 PM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
> > I'm going to push this if no objections.
>
> I took a fresh look at the patch and it LGTM. I only did a few
> cosmetic changes, PFA v7.
>
> Changes since v6 are:
Thank you for looking into this. It appears that I've applied changes
proposed by Mason to v5, not v6. That lead to comment mismatch with
the code that you've noticed. v8 should be correct. Please, recheck.
------
Regards,
Alexander Korotkov
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Allow-locking-updated-tuples-in-tuple_update-and--v8.patch | application/octet-stream | 35.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2023-01-09 10:15:20 | RE: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | John Naylor | 2023-01-09 09:58:11 | Re: [PATCH] Simple code cleanup in tuplesort.c. |