Don't fail for > 1 walsenders in 019_replslot_limit, add debug messages.
authorAndres Freund <andres@anarazel.de>
Mon, 28 Mar 2022 05:29:19 +0000 (22:29 -0700)
committerAndres Freund <andres@anarazel.de>
Mon, 28 Mar 2022 05:35:42 +0000 (22:35 -0700)
commit91c0570a791180aa3ff01d70eb16ed6c0d8283a3
treef27cda06618d00f247d3a7f941759c5846bbf558
parentda4b56662f2cda3ef97847307aaec8e8f66ffb15
Don't fail for > 1 walsenders in 019_replslot_limit, add debug messages.

So far the first of the retries introduced in f28bf667f60 resolves the
issue. But I (Andres) am still suspicious that the start of the failures might
indicate a problem.

To reduce noise, stop reporting a failure if a retry resolves the problem. To
allow figuring out what causes the slow slot drop, add a few more debug
messages to ReplicationSlotDropPtr.

See also commit afdeff10526fe0972ee5e6 and f28bf667f60.

Discussion: https://postgr.es/m/20220327213219.smdvfkq2fl74flow@alap3.anarazel.de
src/backend/replication/slot.c
src/test/recovery/t/019_replslot_limit.pl