Postgres replication slots grow indefinitely

Inactive replication slots cause the accumulation of WAL files on the source DB instances WAL files might fill storage and cause outages Drop the subscription

A replication slot is the mechanism used in this scheme to track progress of a subscription For Aurora PostgreSQL DB clusters, the WAL records are saved on

replication slot already exists I prefer using pg_stat_replication to make monitoring easier Monitoring PostgreSQL replication slots A replication slot ensures that the WAL will not go away

replication slot is active for pid Replication slots make sure that the new primary can carry on streaming changes from where the old primary left off This minimizes data loss