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

When this slot should be active, because you have a secondary site configured using that slot, look for the PostgreSQL logs for the secondary site, to view why

In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to

replication slot Although when a connector is not active, Postgres may allow other connector to consume the replication slot

replication slot does not exist We can have multiple replication slots for a single database; each slot has its own state allowing different consumers to receive changes from