Refactor WaitForLSNReplay() to return the result of waiting
Currently, WaitForLSNReplay() immediately throws an error if waiting for LSN
replay is not successful. This commit teaches WaitForLSNReplay() to return
the result of waiting, while making pg_wal_replay_wait() responsible for
throwing an appropriate error.
This is preparation to adding 'no_error' argument to pg_wal_replay_wait() and
new function pg_wal_replay_wait_status(), which returns the last wait result
status.
Additionally, we stop distinguishing situations when we find our instance to
be not in a recovery state before entering the waiting loop and inside
the waiting loop. Standby promotion may happen at any moment, even between
issuing a procedure call statement and pg_wal_replay_wait() doing a first
check of recovery status. Thus, there is no pointing distinguishing these
situations.
Also, since we may exit the waiting loop and see our instance not in recovery
without throwing an error, we need to deleteLSNWaiter() in that case. We do
this unconditionally for the sake of simplicity, even if standby was already
promoted after reaching the target LSN, the startup process surely already
deleted us.
Reported-by: Michael Paquier
Discussion: https://postgr.es/m/ZtUF17gF0pNpwZDI%40paquier.xyz
Reviewed-by: Michael Paquier, Pavel Borisov
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/73da6b8d1b3e8b7541961c3534e584243cb0470e
Modified Files
--------------
src/backend/access/transam/xlogfuncs.c | 31 ++++++++++++++++++++++++++++++-
src/backend/access/transam/xlogwait.c | 33 +++++++++++----------------------
src/include/access/xlogwait.h | 13 ++++++++++++-
src/tools/pgindent/typedefs.list | 1 +
4 files changed, 54 insertions(+), 24 deletions(-)
