Zalando contributed two features to Debezium to solve WAL growth issues in PostgreSQL logical replication at scale. The first contribution introduced an opt-in `lsn.flush.mode` configuration to prevent WAL accumulation on low-activity databases. The second added `offset.mismatch.strategy` to handle conflicts between stored

11m read time From engineering.zalando.com
Post cover image
Table of contents
The WAL Growth Problem ReturnsDebezium Disables the FixFirst Contribution: Make It Opt-InUnderstanding Why We're DifferentThe Real Problem: When the Slot and Offset DisagreeSecond Contribution: Trust the SlotA Note of GratitudeWhat This Means for You

Sort: