]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Revert 019_replslot_limit.pl related debugging aids.
authorAndres Freund <andres@anarazel.de>
Tue, 5 Jul 2022 18:01:10 +0000 (11:01 -0700)
committerAndres Freund <andres@anarazel.de>
Tue, 5 Jul 2022 18:16:04 +0000 (11:16 -0700)
commit49ddd98763624cfb6020f8b525a021e9788473a5
treebb556d8686fa57b504c22e052e0a6c63ca066920
parentdb1fff1ea43720d7aba41e5f03a62009731e559c
Revert 019_replslot_limit.pl related debugging aids.

This reverts most of 91c0570a791f28bf667f60fe0972ee5e6afdeff10526. The
only thing left is the retry loop in 019_replslot_limit.pl that avoids
spurious failures by retrying a couple times.

We haven't seen any hard evidence that this is caused by anything but slow
process shutdown. We did not find any cases where walsenders did not vanish
after waiting for longer. Therefore there's no reason for this debugging code
to remain.

Discussion: https://postgr.es/m/20220530190155.47wr3x2prdwyciah@alap3.anarazel.de
Backpatch: 15-
src/backend/replication/slot.c
src/backend/storage/lmgr/lwlock.c
src/backend/utils/init/postinit.c
src/bin/pg_basebackup/pg_basebackup.c
src/include/storage/lwlock.h
src/test/recovery/t/019_replslot_limit.pl