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
v4-0002-Document-carrying-tuple-locks-across-UPDATE.patch
Description: Binary data
v4-0001-Avoid-carrying-self-lock-only-xmax-to-updated-tup.patch
Description: Binary data
