Re: pgsql: Set HEAP_XMAX_INVALID for tuples updated by aborted subtransacti

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Set HEAP_XMAX_INVALID for tuples updated by aborted subtransacti
Date: 2026-10-31 00:34:27
Message-ID: auU3k7IXL75TElTn@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Oct 29, 2026 at 05:11:26PM +0900, Michael Paquier wrote:
> As far as I know this is implied since 7b78474da356. So it's been
> around for some time... It's really hard to miss, as the other thread
> has proved.

I meant the opposite here, as of "It's really *easy* to miss, as the
other thread has proved". Sorry for the confusion. :)
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2026-10-31 00:40:59 Re: ZSTD TOAST compression, and an extensible compression method encoding
Previous Message Chao Li 2026-10-31 00:15:55 Re: Return INT_MAX or INT_MIN from strtoint() on overflow

Browse pgsql-committers by date

  From Date Subject
Previous Message Andres Freund 2026-10-30 20:33:59 pgsql: tests: Don't use the initdb template for older installations