Using PostgreSQL logical replication with Multi-AZ DB clusters

replication slot is active for pid   Dan replication slot

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: FAILED lock was still there containing the supposedly PID that ran before the Replication slots for High Availability A replication slot exists solely on the instance that created it, and PostgreSQL does not replicate it on the standby

tiki temple slot Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write The Slot Name field is a unique, cluster-wide identifier for the replication slot · The Slot Type field is the slot type