postgressrcbackendreplication at master

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

Filling the disk causes the database instance to stop serving clients and thus a loss of service Assess the replication slots status via psql : SELECT

replication slot already exists One statistics record of pg_stat_replication_slots is created for each logical replication slot described above Only one receiver may

replication slot does not exist Replication slots make sure that the new primary can carry on streaming changes from where the old primary left off This minimizes data loss