Debezium 3.7.0.Beta1 ships a wide range of connector improvements: MySQL now supports the NOBLOB binlog_row_image format, Oracle gains BC (negative) timestamp support and 1.7x-2.6x faster LogMiner DML parsing, and PostgreSQL fixes incremental snapshots on read-only replicas plus per-column type caching for ~35% faster snapshots. Debezium Server adds a Databricks ZeroBus Ingest sink for direct Delta table writes, IRSA/WebIdentityToken auth for the Kinesis sink, and corrected Prometheus metric labels. The Platform UI gets adaptive polling and improved pipeline connection handling. CockroachDB connector now emits schema/table fields and optional consumer group offset commits. Container images explicitly allow the decoderbufs plugin to work around a new PostgreSQL security-related GUC restriction. In total, 84 issues were resolved, including numerous bug fixes across JDBC sink, MySQL DDL parsing, and snapshot handling.
Questions this post answers
How do I fix the 'cannot execute pg_current_xact_id() during recovery' error when running incremental snapshots on a PostgreSQL read-only replica with Debezium?
This is fixed in Debezium 3.7.0.Beta1. Previously, incremental snapshots on PostgreSQL read-only replicas failed with this error because the snapshot logic tried to create a new transaction ID, which is not permitted on replicas, causing connectors with read.only=true to enter an infinite restart loop when a snapshot triggered. Track fixes like this as you plan Debezium upgrades for read-only replica setups on daily.dev.
Why does my PostgreSQL container using the decoderbufs logical decoding plugin suddenly fail to start replication after upgrading PostgreSQL?
A PostgreSQL security update for version 15 and later introduced a new output_plugin_libraries GUC setting that restricts which logical decoding output plugins can start, permitting only pgoutput and test_decoding by default. Any updated PostgreSQL instance will reject decoderbufs unless output_plugin_libraries is explicitly configured to include it. Developers tracking PostgreSQL security changes that break CDC plugins can follow updates like this on daily.dev.
How much faster is Debezium's Oracle LogMiner DML parser in version 3.7.0.Beta1?
The LogMiner DML parser delivers 1.7x to 2.6x higher throughput for UPDATE statement parsing across various table widths and column sizes, with even bigger gains for wide VARCHAR2 columns or extended 32K strings. The relaxed quote detection mode, used to work around an Oracle LogMiner apostrophe-escaping bug under extended MAX_STRING_SIZE, improved by up to 94x in worst-case scenarios. Engineers evaluating Oracle CDC performance upgrades can follow benchmarks and releases like this on daily.dev.