| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, 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-03 14:12:09 |
| Message-ID: | CALT9ZEGMyqaa2VNWYwCguZoZdExNv2agcthnUF78GHi_0wCh4g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Upon Alexander reverting patches v15 from master, I've rebased what
was correction patches v4 in a message above on a fresh master
(together with patches v15). The resulting patch v16 is attached.
Pavel.
| Attachment | Content-Type | Size |
|---|---|---|
| v16-0002-Add-EvalPlanQual-delete-returning-isolation-test.patch | application/octet-stream | 3.4 KB |
| v16-0001-Allow-locking-updated-tuples-in-tuple_update-and.patch | application/octet-stream | 60.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-04-03 14:19:49 | Re: [EXTERNAL] Re: [PATCH] Report the query string that caused a memory error under Valgrind |
| Previous Message | Ashutosh Bapat | 2023-04-03 14:11:37 | Re: Infinite Interval |