Re: [PATCH v2] Avoid carrying self lock-only xmax to updated tuple

From: Chee Wooson <chee(dot)wooson(at)gmail(dot)com>
To: João Rito <joaovictor(dot)rito(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH v2] Avoid carrying self lock-only xmax to updated tuple
Date: 2026-11-12 03:26:34
Message-ID: CAMfungPvsvmLdTymz_3j6KiHSgDyohn5eB6-BthhpGr+=X3eJg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi João,

Thanks for taking the time to test the patch and for sharing the
detailed results. I really appreciate your help!

Best regards,
Chee Wooson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message João Rito 2026-11-12 03:41:39 Re: [PATCH] Fix interval input at minimum signed field values (BUG #19746)
Previous Message Xuneng Zhou 2026-11-12 03:18:01 Re: Fix resource leaks in pg_receivewal on LZ4 close failures