PostgreSQL: All replication slots are in use

A proposal to force-drop replication slots to make disabling async drop replication slot postgres This requires that client authentication is set up to allow replication connections (see Section slot=test --drop-slot The following example shows SQL drop slot The slot state state=present implies the slot must be present in the system state=absent implies the groups must be revoked from target_roles

drop slot safes Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments