Re: Consistently use the XLogRecPtrIsInvalid() macro

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Quan Zongliang <quanzongliang(at)yeah(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Consistently use the XLogRecPtrIsInvalid() macro
Date: 2025-11-19 17:53:31
Message-ID: opbwhjrkfvymrdpmgkkxw5ykivzf5niwe6maqx65iihbuvwd3d@qo2trdqrkyuu
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-11-19 12:27:30 -0500, Robert Haas wrote:
> It's possible, but fundamentally I think it's about replacing
> XLogRecPtrIsInvalid with XLogRecPtrIsValid, and what I'm saying is I
> wouldn't have chosen to do that. I agree that it would have been
> better to do it that way originally, but I disagree with paying the
> switching cost, especially in the back-branches.

+1

This just seems like a lot of noise for something at most very mildly odd.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2025-11-19 18:00:29 Re: Expanding HOT updates for expression and partial indexes
Previous Message Fujii Masao 2025-11-19 17:50:37 Re: CREATE/ALTER PUBLICATION improvements for syntax synopsis