It seems like you're experiencing an issue with disk space usage when using Change Data Capture (CDC) with Airbyte on your Postgres database. This is a known behavior as CDC replication increases disk space used on the database server. The additional data is stored until it is consumed. This is due to how Postgres CDC is implemented - each destination would receive only part of the data available in the replication slot [[source](
https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting)]. Here are a few suggestions to manage this: 1.
Set frequent syncs for CDC: This ensures that the data doesn't fill up your disk space. The more frequently you sync, the less data is stored in the replication slot at any given time. 2.
Delete the replication slot when not in use: If you stop syncing a CDC-configured Postgres instance with Airbyte, it's recommended to delete the replication slot. Otherwise, it may continue to fill up your disk space. 3.
Monitor your disk space usage: Keep an eye on your disk space usage and adjust your sync frequency or other settings as needed to ensure you don't run out of space. Before you proceed with adding this to your production database, it would be wise to consider these factors and perhaps run more tests on a development or staging environment to better understand the impact on your specific setup. Also, remember that for CDC, you must connect to primary/master databases. Pointing the connector configuration to replica database hosts for CDC will lead to failures [[source](
https://docs.airbyte.com/integrations/sources/postgres)]. If you continue to experience issues, you might want to consider reaching out to the Airbyte community on their [forum](
https://discuss.airbyte.io) or [Slack](
https://airbytehq.slack.com) for more specific guidance.