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

From Bertrand Drouvot
Subject Re: Consistently use the XLogRecPtrIsInvalid() macro
Date
Msg-id aR4CroIPon7zoJe/@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Consistently use the XLogRecPtrIsInvalid() macro  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Consistently use the XLogRecPtrIsInvalid() macro
List pgsql-hackers
Hi,

On Wed, Nov 19, 2025 at 12:27:30PM -0500, Robert Haas wrote:
> On Wed, Nov 19, 2025 at 11:49 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> > > 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.
> >
> > No, they don't need to.  Thus far, they can still keep their code the
> > way it is.
> 
> True, but if they write any new code, and care about it compiling with
> older minor releases, this is a potential pitfall.

Why given that 06edbed4786 has been back patched through 13?

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Post-release followup: pg_add_size_overflow()
Next
From: Fujii Masao
Date:
Subject: Re: CREATE/ALTER PUBLICATION improvements for syntax synopsis