Re: New WAL record to detect the checkpoint redo location - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: New WAL record to detect the checkpoint redo location
Date
Msg-id CAFiTN-uJ7AYcS4nnrTUYQbR1dYwaF45eKzdmi_MrOz+C9pS-4A@mail.gmail.com
Whole thread Raw
In response to Re: New WAL record to detect the checkpoint redo location  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: New WAL record to detect the checkpoint redo location
List pgsql-hackers
On Fri, Aug 18, 2023 at 10:12 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Fri, Aug 18, 2023 at 5:24 AM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Thu, Aug 17, 2023 at 01:11:50PM +0530, Dilip Kumar wrote:
> > > Yeah right, actually I was confused, I assumed it will return the
> > > start LSN of the record.  And I do not see any easy way to identify
> > > the Start LSN of this record so maybe this solution will not work.  I
> > > will have to think of something else.  Thanks for pointing it out.
> >
> > About that.  One thing to consider may be ReserveXLogInsertLocation()
> > while holding the WAL insert lock, but you can just rely on
> > ProcLastRecPtr for the job after inserting the REDO record, no?
>
> Yeah right, we can use ProcLastRecPtr.  I will send the updated patch.

Here is the updated version of the patch.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: broken master regress tests
Next
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby