Re: Implement waiting for wal lsn replay: reloaded - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Implement waiting for wal lsn replay: reloaded
Date
Msg-id CAPpHfdtK8NRxo1-u6kh1DjRGpcngBnHr5bahiY_5utWAbOjBDQ@mail.gmail.com
Whole thread Raw
In response to Re: Implement waiting for wal lsn replay: reloaded  (Andres Freund <andres@anarazel.de>)
Responses Re: Implement waiting for wal lsn replay: reloaded
List pgsql-hackers
Hi!

On Mon, Nov 3, 2025 at 5:13 PM Andres Freund <andres@anarazel.de> wrote:
> On 2025-11-03 16:06:58 +0100, Álvaro Herrera wrote:
> > On 2025-Nov-03, Alexander Korotkov wrote:
> >
> > > I'd like to give this subject another chance for pg19.  I'm going to
> > > push this if no objections.
> >
> > Sure.  I don't understand why patches 0002 and 0003 are separate though.
>
> FWIW, I appreciate such splits. Even if the functionality isn't usable
> independently, it's still different type of code that's affected. And the
> patches are each big enough to make that worthwhile for easier review.

Thank you for the feedback, pushed.

> One thing that'd be nice to do once we have WAIT FOR is to make the common
> case of wait_for_catchup() use this facility, instead of polling...

The draft patch for that is attached.  WAIT FOR doesn't handle all the
possible use cases of wait_for_catchup(), but I've added usage when
it's appropriate.

------
Regards,
Alexander Korotkov
Supabase

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Teaching planner to short-circuit empty UNION/EXCEPT/INTERSECT inputs
Next
From: Xuneng Zhou
Date:
Subject: Re: [PATCH] Fix fragile walreceiver test.