Troubleshoot a PostgreSQL AWS DMS task with used replication slots

The morale of the story? Don't leave your replication slots unattended! There shouldn't be any slots which are inactive for too long For

A PostgreSQL replication slot is a vital feature ensuring the master server retains necessary Write-Ahead Log files, even when replicas

drop slot safes Are these orphan replication slots? They are removed when I drop the subscription, but are created again when I create the subscription again

drop replication slot Deleting a slot that's currently being used by a replica can cause replication issues, leading to potential data loss