Re: [HACKERS] make async slave to wait for lsn to be replayed

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Kartyshov Ivan <i.kartyshov@postgrespro.ru>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Amit Kapila <amit.kapila16@gmail.com>, dilipbalaut@gmail.com, smithpb2250@gmail.com, pgsql-hackers@lists.postgresql.org

Date: 2024-03-28T07:36:32Z

Lists: pgsql-hackers

> v12

Hi all,

I didn't review the patch but one thing jumped out: I don't think it's
OK to hold a spinlock while (1) looping over an array of backends and
(2) making system calls (SetLatch()).

Commits

Ensure standby promotion point in 043_wal_replay_wait.pl
- 2520226c953c 18.0 landed
Minor cleanup related to pg_wal_replay_wait() procedure
- 85b98b8d5a48 18.0 landed
Adjust pg_wal_replay_wait() procedure behavior on promoted standby
- 867d396ccd2a 18.0 landed
pg_wal_replay_wait(): Fix typo in the doc
- 8036d73ae3d4 18.0 landed
Implement pg_wal_replay_wait() stored procedure
- 3c5db1d6b016 18.0 landed
- 06c418e163e9 17.0 landed
Revert: Implement pg_wal_replay_wait() stored procedure
- 772faafca1b2 17.0 landed
Call WaitLSNCleanup() in AbortTransaction()
- 74eaf66f988c 17.0 landed
Clarify what is protected by WaitLSNLock
- ee79928441e7 17.0 landed
Use an LWLock instead of a spinlock in waitlsn.c
- 25f42429e2ff 17.0 landed
Use the pairing heap instead of a flat array for LSN replay waiters
- bf1e65080629 17.0 landed
Minor improvements for waitlsn.c
- e37662f22158 17.0 landed
Make the order of the header file includes consistent
- 97d85be36544 17.0 cited