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

From Bertrand Drouvot
Subject Re: Consistently use the XLogRecPtrIsInvalid() macro
Date
Msg-id aQ4KJws+Bx4C20nK@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Consistently use the XLogRecPtrIsInvalid() macro  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: Consistently use the XLogRecPtrIsInvalid() macro
Re: Consistently use the XLogRecPtrIsInvalid() macro
List pgsql-hackers
Hi,

On Fri, Nov 07, 2025 at 02:37:32PM +0100, Álvaro Herrera wrote:
> On 2025-Nov-07, Bertrand Drouvot wrote:
> 
> > Agree, will modify the .cocci scripts that way.
> 
> I just noticed that we missed this ... maybe you want to include it also?
> 
> -    MyProc->waitLSN = 0;
> +    MyProc->waitLSN = InvalidXLogRecPtr;
>  
> -    lastLSN = 0;
> +    lastLSN = InvalidXLogRecPtr;
>  
> -    MyProc->waitLSN = 0;
> +    MyProc->waitLSN = InvalidXLogRecPtr;

Yeah, that's another story here that is worth to look at too. Will do.

I'm currently working on the RegProcedureIsValid() and OidIsValid() cases,
will share once done.

> 
> > Now that XLogRecPtrIsValid() is available in back branches, I agree that we
> > can be less conservative and not wait until v24. v21 looks like good timing to
> > me.
> 
> Cool,  please resubmit.

Sure, done in the attached.

Regards,

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

Attachment

pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Xlogprefetcher: Use atomic add for increment counter
Next
From: Andres Freund
Date:
Subject: Re: LTO aggressively optimizing out function despite explicit calls in logical decoding