<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zero-Downtime on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/zero-downtime/</link>
    <description>Recent content in Zero-Downtime on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/zero-downtime/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Zero-Downtime Postgres Schema Changes in 2026: pgroll vs Reshape vs graphile-migrate</title>
      <link>https://www.pistack.xyz/posts/2026-10-26-postgres-zero-downtime-migrations-pgroll-reshape-graphile-migrate/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-26-postgres-zero-downtime-migrations-pgroll-reshape-graphile-migrate/</guid>
      <description>&lt;p&gt;&lt;code&gt;ALTER TABLE users ADD COLUMN email_verified boolean NOT NULL DEFAULT false;&lt;/code&gt; on a table with 40 million rows takes a lock. In Postgres 11+ adding a column with a non-volatile default is metadata-only, so that particular statement is safe — but &lt;code&gt;ALTER COLUMN ... TYPE&lt;/code&gt;, adding a constraint, or backfilling a new index will still queue behind every open transaction and block all writes behind it. One long-running analytics query, and your &amp;ldquo;quick migration&amp;rdquo; becomes a five-minute outage.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
