Suppose a CDC data loading tool (Fivetran, Airbyte, Debezium, etc) gets into a failure state and is not successfully running its incremental syncs of a Postgres data source. Also suppose that max_slot_wal_keep_size is set to -1. As far as I can tell, this means that the amount of WAL retained for the tool's replication slot will be allowed to grow without bounds.
My question: assuming the tables continue to grow, is the end state of this scenario that the WAL eventually fills up all disk space, causing total catastrophe for the production database? Does the answer depend on whether the tool is pointed at read-only replica of the database?
max_slot_wal_keep_sizeis set to -1.... will the hard drive of the database begin to completely fill up?