How is logical replication supposed to work with Patroni?

replication slot is active for pid   Dan replication slot does not exist

And this finally explains why that inactive replication slot causes the retention of that much WAL on an idle database: there actually are some

replication slot is already in use Here is the error from log: 2022 Powered by Discourse, best viewed with JavaScript enabled  pid 23095 usesysid 169593 usename repmgr application_name active t active_pid 6689 xmin catalog_xmin restart_lsn

gas stations with slot machines near me Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or stuck in production The Slot Name field is a unique, cluster-wide identifier for the replication slot · The Slot Type field is the slot type