<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Postgres on Sauvik Biswas</title>
    <link>https://sauvikbiswas.com/tags/postgres/</link>
    <description>Recent content in Postgres on Sauvik Biswas</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sauvikbiswas.com/tags/postgres/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debezium and the growing pg_wal</title>
      <link>https://sauvikbiswas.com/posts/debezium-and-growing-pg-wal/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://sauvikbiswas.com/posts/debezium-and-growing-pg-wal/</guid>
      <description>&lt;h1 class=&#34;heading&#34; id=&#34;a-problem-in-production&#34;&gt;&#xA;  A problem in production&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#a-problem-in-production&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;A couple of days ago, our stack saw a massive rise in WAL. As a side effect, we weren&amp;rsquo;t seeing Debezium emit CDC messages to Kafka, which in turn affected some critical workflows from advancing. This was not the first time this had happened. One idea that was thrown around was to limit the tables Debezium subscribes to. However, that doesn&amp;rsquo;t help.&lt;/p&gt;&#xA;&lt;p&gt;Limiting which tables Debezium subscribes to (via the Postgres &lt;code&gt;PUBLICATION&lt;/code&gt;) reduces the &lt;strong&gt;events Debezium emits&lt;/strong&gt;, but it does &lt;strong&gt;not&lt;/strong&gt; reduce what Postgres has to &lt;strong&gt;keep on disk&lt;/strong&gt;. WAL retention is governed by the &lt;em&gt;replication slot&lt;/em&gt;, not by the publication. If the slot doesn&amp;rsquo;t advance, &lt;code&gt;pg_wal&lt;/code&gt; keeps growing, even if Debezium is &amp;ldquo;quiet.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
