Re: New WAL record to detect the checkpoint redo location

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New WAL record to detect the checkpoint redo location
Date: 2023-08-25 05:38:25
Message-ID: CAFiTN-uJ7AYcS4nnrTUYQbR1dYwaF45eKzdmi_MrOz+C9pS-4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 18, 2023 at 10:12 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Fri, Aug 18, 2023 at 5:24 AM Michael Paquier <michael(at)paquier(dot)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 Content-Type Size
v3-0001-New-WAL-record-for-checkpoint-redo-location.patch application/octet-stream 6.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-08-25 05:39:01 Re: Synchronizing slots from primary to standby
Previous Message Thomas Munro 2023-08-25 05:37:29 Re: broken master regress tests