| 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-18 04:42:00 |
| Message-ID: | CAFiTN-s=p8poaRTK0H1VzH2YPV2CXMow9bJrC83ww4N+mDBjWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2023-08-18 05:02:55 | Re: Extract numeric filed in JSONB more effectively |
| Previous Message | Peter Smith | 2023-08-18 03:51:38 | Re: [PoC] pg_upgrade: allow to upgrade publisher node |