Stabilize 019_replslot_limit.pl: wait on slot restart_lsn

Alexander Korotkov <akorotkov@postgresql.org>

Commit: cdb1d1cf1de63b5dfecd5ebb23fd277b0e767f57
Author: Alexander Korotkov <akorotkov@postgresql.org>
Date: 2026-05-26T23:54:04Z
Stabilize 019_replslot_limit.pl: wait on slot restart_lsn

wait_for_catchup() has "wait for the standby to reach the target LSN"
semantics.  However, the previous polling implementation actually waited for
the primary to observe that position via pg_stat_replication.
7e8aeb9e483 introduced the new WAIT FOR LSN-based implementation, which
just probes the standby.

019_replslot_limit.pl relied on the old side effect: its
"slot state changes to extended/unreserved" subtests inspect
primary-side pg_replication_slots, whose wal_status depends on
restart_lsn, which only advances after the walsender processes a
standby reply.  Make the test wait on what it actually needs by
replacing each wait_for_catchup() with
wait_for_slot_catchup('rep1', 'restart', primary->lsn('write')).

Reported-by: Alexander Lakhin <exclusion@gmail.com>
Discussion: https://postgr.es/m/63f6abc9-c0ae-465d-a4e6-667eca6ea008@gmail.com
Author: Xuneng Zhou <xunengzhou@gmail.com>
Author: Alexander Korotkov <aekorotkov@gmail.com>

Files

PathChange+/−
src/test/recovery/t/019_replslot_limit.pl modified +14 −6

Discussion