pg_wal eat disk because inactive replication slot #2012

We were able to successfully stop the PID on the primary and then drop the replication slot using SELECT pg_drop_replication_slot

Unused slots can be dropped to remove WAL segments using the pg_drop_replication_slot command The replica instance is using too much memory The replica uses

nongki 99 slot Attempt to terminate all existing connections to the target database It doesn't terminate if prepared transactions, active logical replication slots or

best in slot ret paladin I need to know how this should be approached once I put this thing in prod, as deleting the replication slot is just a workaround Another query