<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Snapshots on Nikita Ryanov</title><link>https://nryanov.com/tags/snapshots/</link><description>Recent content in Snapshots on Nikita Ryanov</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 01 Jan 2026 04:30:00 +0300</lastBuildDate><atom:link href="https://nryanov.com/tags/snapshots/index.xml" rel="self" type="application/rss+xml"/><item><title>Debezium: unforeseen difficulties</title><link>https://nryanov.com/postgresql/debezium-production-issues/</link><pubDate>Thu, 01 Jan 2026 04:30:00 +0300</pubDate><guid>https://nryanov.com/postgresql/debezium-production-issues/</guid><description>&lt;p&gt;In this article I want to share problems I faced while running Debezium in production with PostgreSQL, and solutions where they exist.
This material is based on a talk I gave at SmartData 2025. I assume that you already know what CDC is and how Debezium works in general — if not, start with &lt;a href="https://nryanov.com/postgresql/debezium-postgres/"&gt;PostgreSQL: Log-based CDC using debezium&lt;/a&gt; and &lt;a href="https://nryanov.com/kafka/kafka-connect-overview/"&gt;Kafka-connect: overview&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;All examples below were tested with PostgreSQL 15, 16 and 17. If a version is not mentioned explicitly, PostgreSQL 17 is assumed.
Examples are implemented using a runtime wrapper around Debezium Engine, but the same problems and solutions apply to the Kafka Connect connector, Debezium Server, and other deployment options.&lt;/p&gt;</description></item></channel></rss>