Re: [PATCH v1 1/1] Avoid carrying self lock-only xmax to updated tuple

From:	Chee Wooson <chee(dot)wooson(at)gmail(dot)com>
To:	pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject:	Re: [PATCH v1 1/1] Avoid carrying self lock-only xmax to updated tuple
Date:	2026-09-03 09:56:25
Message-ID:	CAMfungOo86-ANcXoa-QNqOQmBAXNjDvAQYnhRd=m=fiEU4p7pA@mail.gmail.com
Views:	Whole Thread | Raw Message | Download mbox | Resend email
Thread:	2026-09-03 09:27:37 from "chee(dot)wooson" <chee(dot)wooson(at)gmail(dot)com>  2026-09-03 09:27:38 from "chee(dot)wooson" <chee(dot)wooson(at)gmail(dot)com>   2026-09-03 09:56:25 from Chee Wooson <chee(dot)wooson(at)gmail(dot)com> 📎    2026-09-03 11:26:25 from Chee Wooson <chee(dot)wooson(at)gmail(dot)com> 📎
Lists:	pgsql-hackers

Attachment	Content-Type	Size
v1-0001-Avoid-carrying-self-lock-only-xmax-to-updated-tup.patch	application/octet-stream	9.5 KB

In response to

• [PATCH v1 1/1] Avoid carrying self lock-only xmax to updated tuple at 2026-09-03 09:27:38 from chee.wooson

Responses

• [PATCH v2] Avoid carrying self lock-only xmax to updated tuple at 2026-09-03 11:26:25 from Chee Wooson

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Himanshu Upadhyaya	2026-09-03 10:00:00	Re: Fire create_upper_paths_hook for UPPERREL_PARTIAL_GROUP_AGG
Previous Message	Tender Wang	2026-09-03 09:39:30	Re: Assert failure in try_nestloop_path()