Postgres replication slots grow indefinitely

Postgres replication slots grow indefinitely drop replication slot If you are not actively consuming a replication slot you should drop it To drop a replication slot called test_slot using SQL: SELECT drop slot safe Used replication slots continue to occupy space If you run multiple AWS DMS tasks or you have old tasks that run on the same DB instance, then remove the used

drop slot safe On the primary site's database node, start a PostgreSQL console session: sudo gitlab-psql · Find the name of the relevant replication slot · Remove the

drop slot You must monitor logical decoding Any unused replication slot must be dropped Slots hold on to Postgres WAL logs and relevant system catalogs Make sure to manually delete open slots Note that DMS automatically drops replication slots when the task is deleted, if DMS created the slot Set