Re: pgsql: Implement pg_wal_replay_wait() stored procedure

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Alexander Korotkov <akorotkov@postgresql.org>, pgsql-committers@lists.postgresql.org

Date: 2024-09-26T22:04:19Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Revert pg_wal_replay_wait() stored procedure
- 3a7ae6b3d91e 18.0 landed
Add 'no_error' argument to pg_wal_replay_wait()
- e546989a269d 18.0 landed
Refactor WaitForLSNReplay() to return the result of waiting
- 73da6b8d1b3e 18.0 landed
Make WaitForLSNReplay() issue FATAL on postmaster death
- 6cfebfe88b9a 18.0 landed
Move LSN waiting declarations and definitions to better place
- 5035172e4ab5 18.0 landed
Update oid for pg_wal_replay_wait() procedure
- e658038772f5 18.0 landed
Move pg_wal_replay_wait() to xlogfuncs.c
- 014f9f34d252 18.0 landed
Implement pg_wal_replay_wait() stored procedure
- 3c5db1d6b016 18.0 cited

On Thu, Sep 26, 2024 at 06:41:18PM +0300, Alexander Korotkov wrote:
> On Thu, Sep 26, 2024 at 11:19 AM Michael Paquier <michael@paquier.xyz> wrote:
>> Please use something in the 8000-9999 range, as required by
>> 98eab30b93d5.
> 
> Fixed, sorry for messing this up.

Thanks for taking care of that.

> I would appreciate if you have time to look at [0] to check if it
> meets your expectations.
> 
> Links.
> 1. https://www.postgresql.org/message-id/CAPpHfdsw9oq62Fvt65JApHJf1auUirdGJV7%3DnRyVnDL3M8z5xA%40mail.gmail.com

I am aware of this one, sorry for the delay.  It's on my pile of
things to look at, but I have not been able to get back to it.
--
Michael