Request a Demo
Home   >   mailing lists

[PATCH v2] Avoid carrying self lock-only xmax to updated tuple - Mailing list pgsql-hackers

From Chee Wooson
Subject [PATCH v2] Avoid carrying self lock-only xmax to updated tuple
Date
Msg-id CAMfungPiUSxdTR+HNRhV0sVXTQgguFtuWgVrGBFKSY8dpgyC3w@mail.gmail.com
Whole thread
In response to [PATCH v1 0/1] Avoid carrying self lock-only xmax to updated tuple  ("chee.wooson" <chee.wooson@gmail.com>)
List pgsql-hackers
Tree view
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

pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Follow-up review items for update_deleted
Next
From: Nisha Moond
Date:
Subject: Re: Follow-up review items for update_deleted