Files
repmgr/doc
Ian Barwick 9273e7af73 "standby switchover": avoid potential race condition with WAL location check
Immediately after the demotion candidate (primary) has shut down, we can't
be absolutely sure that the walreceiver has flushed all WAL to disk, so
checking pg_last_wal_receive_lsn() at that point might not reflect
the actual last available WAL location.

To handle this, we'll loop for a while (timeout controlled by configuration
parameter "wal_receive_check_timeout") before finally deciding whether
the standby is still behind the shut-down primary.

Addresses issue raised in GitHub #518.
2019-02-01 12:06:22 +09:00
..
2019-01-21 17:37:01 +05:30
2017-10-17 11:00:37 +09:00
2019-01-21 14:54:35 +09:00
2018-04-24 21:08:05 +09:00
2017-10-05 10:30:28 +09:00
2017-10-05 10:30:28 +09:00
2017-10-05 10:30:29 +09:00