Re: Consistently use the XLogRecPtrIsInvalid() macro - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Consistently use the XLogRecPtrIsInvalid() macro
Date
Msg-id CA+TgmoZi28-mfUeaKOs6GvT69EDDngUSC521rcwGfhBXeqv3nw@mail.gmail.com
Whole thread Raw
In response to Re: Consistently use the XLogRecPtrIsInvalid() macro  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: Consistently use the XLogRecPtrIsInvalid() macro
List pgsql-hackers
On Thu, Nov 6, 2025 at 2:48 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> Okay, thanks, I have applied that one to all stable branches, except I
> didn't add the judgemental comment about XLogRecPtrIsInvalid().

I'm rather late to the party here, but for what it's worth, I don't
really think this was a good idea. Anyone who wants to write
out-of-core code that works in the back-branches must still write it
the old way, or it will potentially fail on older minor releases. Over
the alternative actually chosen, I would have preferred (a) not doing
this project at all or (b) making a hard switch in master to use the
new macro everywhere and remove the old one, while leaving the
back-branches unchanged or (c) dropping the use of the macro
altogether, in that order of preference.

That sad, I'm not arguing for a revert. My basic position is that this
wasn't worth the switching cost, not that it was intrinsically a bad
idea.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Trigger more frequent autovacuums of heavy insert tables
Next
From: Heikki Linnakangas
Date:
Subject: Re: POC: make mxidoff 64 bits