Uh oh!
There was an error while loading. Please reload this page.
Remove unused physical replication slot from pgBackRest Patroni setup - #993
Remove unused physical replication slot from pgBackRest Patroni setup#993ghorbani-ali wants to merge 2 commits into
Conversation
jeltz
commented
Jul 14, 2026
Thanks for the PR and I agree with the issue but I am not convinced about the fix. Maybe we instead should just include only the keys relevant to PgBackRest and leave everything else out? |
jeltz
commented
Jul 14, 2026
Small thing: we do not use prefixes like |
Hi @jeltz Thanks for replay. Yes I agree with you. I didn’t know whether this would be accepted by you. Also I realized same code block exist on all other versions. I’m going to update my PR and keep just parts that relevant to PgBackRest. Please Let me know if there's anything else. |
jeltz
commented
Aug 6, 2026
If you fix it for one version we can fix it in the rest. |
ghorbani-ali
commented
Aug 12, 2026
I updated my PR. Let me know if any additional changes are required. |
Description
Summary
This PR removes the following permanent physical replication slot from the Patroni configuration example in the pgBackRest setup guide:
Why this change is helpful
The guide currently defines a permanent physical replication slot, but it does not configure a standby or another client to consume it.
If the slot remains inactive, PostgreSQL may continue retaining WAL for it. Over time, this can lead to unexpected growth of the
pg_waldirectory and, in some cases, increased disk usage.After setting up pgBackRest for the cluster by following the documentation, this configuration block caused excessive WAL retention. The resulting disk usage eventually filled the available storage and led to a serious outage.
What changed
percona_cluster_1physical replication slot from the Patroni configuration example.use_slots: trueunchanged, so Patroni can continue managing replication slots for cluster members.References