| From: | Chee Wooson <chee(dot)wooson(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | [PATCH v2] Avoid carrying self lock-only xmax to updated tuple |
| Date: | 2026-09-03 11:26:25 |
| Message-ID: | CAMfungPiUSxdTR+HNRhV0sVXTQgguFtuWgVrGBFKSY8dpgyC3w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Attached is v2 of the patch.
This version removes the pageinspect test and updates the existing
ON CONFLICT DO UPDATE regression test to reflect the new behavior:
a self-owned lock-only xmax is no longer carried to the new tuple.
The patch only changes the same-XID, single-XID, lock-only case.
Remote lockers and MultiXacts retain the existing behavior.
The relevant regression tests pass.
Comments and review are welcome.
Regards,
chee wooson
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Avoid-carrying-self-lock-only-xmax-to-updated-tup.patch | application/octet-stream | 7.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2026-09-03 11:36:00 | Re: Follow-up review items for update_deleted |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-09-03 11:09:54 | RE: Follow-up review items for update_deleted |