Re: Consistently use the XLogRecPtrIsInvalid() macro

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: 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-18 15:54:32
Message-ID: 8fb41a19-1d01-41fa-958a-66cce47d1e2b@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18.11.25 10:06, Bertrand Drouvot wrote:
> Hi,
>
> On Fri, Nov 07, 2025 at 03:03:03PM +0000, Bertrand Drouvot wrote:
>> I'm currently working on the RegProcedureIsValid() and OidIsValid() cases,
>> will share once done.
>
> here they are, I'm not creating a new thread for those as this is the same
> kind of ideas (but for other types) but can create a dedicated one if you prefer.

I don't like this change.

RegProcedureIsValid() doesn't add any value over OidIsValid, and we
don't have any RegXXXIsValid() for any of the other regxxx types. So if
we were to do anything about this, I would just remove it.

For OidIsValid etc., I don't think this improves the notation. It is
well understood that InvalidOid is 0. I mean, some people like writing
if (!foo) and some like writing if (foo == NULL), but we're not going to
legislate one over the other. But we're certainly not going to
introduce, uh, if (PointerIsValid(foo)), and in fact we just removed
that! What you're proposing here seem quite analogous but in the
opposite direction.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-11-18 15:59:00 Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
Previous Message jian he 2025-11-18 15:43:13 IS JSON predicate support for domain base type as JSON/JSONB/BYTEA/TEXT