<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Durability on Nalar</title>
    <link>https://nalar.dev/tags/durability/</link>
    <description>Recent content in Durability on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/durability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL Full-Page Writes Raise WAL Volume After Checkpoints</title>
      <link>https://nalar.dev/postgresql-full-page-writes-raise-wal-volume-after-checkpoints/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/postgresql-full-page-writes-raise-wal-volume-after-checkpoints/</guid>
      <description>&lt;p&gt;A PostgreSQL page modified for the first time after a checkpoint can generate much more WAL than a later modification to the same page. With &lt;code&gt;full_page_writes&lt;/code&gt; enabled, the first protected change records a full page image so crash recovery can reconstruct a page even if an operating-system failure interrupts a physical page write.&lt;/p&gt;&#xA;&lt;p&gt;That protection creates a recurring WAL pattern tied to checkpoint boundaries. A checkpoint resets the condition for pages, and subsequent writes gradually encounter pages that need a new full page image.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
