Status: Closed (View Workflow)
Affects Version/s: 0.8.1.Final
Fix Version/s: 1.0.0.Beta1
After deploying the Debezium connector for Postgres in our unstable environment we faced our Postgres instance quickly running out of space.
We have a Postgres instance where we have two databases: production and unstable.
The connector is configured to capture changes from the unstable database. The changes on unstable are few and the connector works correctly.
However, the traffic on the production database is quite high and we noticed that the disk space increases monotonically until we almost ran out of disk space.
After stopping the connector and deleting the replication slot, the disk space was freed up.
It appears to me that `replication_slots` in Postgres work across databases and the Connector is not listening to the event of other databases.