Troubleshoot a PostgreSQL AWS DMS task with used replication slots

Troubleshoot a PostgreSQL AWS DMS task with used replication slots replication slot does not exist Now back on the master server, you should be able to see the replication slot called pgstandby1 when you open the pg_replication_slots view as replication slot does not exist replication slot geo_secondary_my_domain_com does not exist? This occurs when PostgreSQL does not have a replication slot for the secondary node by that name

replication slot does not exist slot does not exist Replicate will create it and then use the slot Or you may use an internal parameter slotName to specify the given slot

replication slot is active for pid do not use it for this lab to avoid extra charges to your account Specify the replication slot name as test_replication Specify the 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