Set up your PostgreSQL source

SELECT * FROM pg_replication_slots to see if any replication slots were accidentally created that might be preventing WAL cleanup · SHOW

Logical replication slots are used to track the WAL positions on the primary server so that the standby server can request

postgresql drop replication slot A replication slot has an identifier that is unique across all databases in a PostgreSQL cluster Slots persist independently of the connection using them and

postgresql create replication slot 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