| From: | Chee Wooson <chee(dot)wooson(at)gmail(dot)com> |
|---|---|
| To: | Joao Rito <joaovictor(dot)rito(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH v2] Avoid carrying self lock-only xmax to updated tuple |
| Date: | 2026-11-17 03:20:52 |
| Message-ID: | CAMfungNn7dT19hzSk3R+JuJCRaPwuRYTDzKU75Utv8PF24XPJw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Joao,
My earlier v3 mail went only to you. Attached is v4, with the
README.tuplock changes revised following your comments.
The README now explains the general carry-forward mechanism before
introducing the same-XID exception. It covers different-subtransaction
lockers and MultiXact handling, shows the exact condition, uses consistent
flag names, and explains why omitting the self-owned lock is safe even
when the updating subtransaction aborts.
Patch 0001 (code and regression test) is unchanged from v3.
Only patch 0002 (README.tuplock) has changed.
The core regression, isolation, and relevant contrib tests passed for
the unchanged implementation.
Thanks again for the testing and review.
Regards,
Chee Wooson
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0002-Document-carrying-tuple-locks-across-UPDATE.patch | application/octet-stream | 3.5 KB |
| v4-0001-Avoid-carrying-self-lock-only-xmax-to-updated-tup.patch | application/octet-stream | 4.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raja Sai pranav | 2026-11-17 04:17:06 | Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup |
| Previous Message | Henson Choi | 2026-11-17 03:03:24 | [DEPARSE] Column alias lists of XMLTABLE and JSON_TABLE are not printed |