Troubleshoot a PostgreSQL AWS DMS task with used replication slots

A replication slot keeps track of the last LSN that its connected replica has received Every time a replica successfully

Postgres replication slot size keeps growing even though Debezium is consuming the WAL This consequently causes to run out of disk space The problem is also

slot draaiknop Failure cause: The specified replication slot already exists in source database Handling suggestion: Delete the replication slot from the

bonus slot new member 100 The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL