Troubleshoot a PostgreSQL AWS DMS task with used replication slots

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

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

drop slot safes replication slot mysub on publisher CREATE SUBSCRIPTION The -- pause replication ALTER SUBSCRIPTION mysub DISABLE; --

drop em slot demo The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the