A proposal to force-drop replication slots to make disabling async

replication slot is active for pid   Dan replication slot postgres

ERROR: could not create replication slot sub1: ERROR: all ERROR: replication origin with OID 1 is already active for PID 5566

Replication Slot edf_tc1_2c59ae112747afa1 is active with PID 101120 in database postgres Slot Restart LSN 1B982ED98 Slot Flush LSN 1B982ED98  In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to

slot spadegaming replication slot started lagging replication activity connection accepted events connection closed events Specifies a file location to store the process ID of the mongos process