<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Upgrade on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/upgrade/</link>
    <description>Recent content in Upgrade on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/upgrade/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Database Major Version Upgrades: pg_upgrade vs Logical Replication vs Dump/Restore</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-database-major-version-upgrades-pgupgrade-logical-replication-dump-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-database-major-version-upgrades-pgupgrade-logical-replication-dump-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every database administrator eventually faces the same challenge: upgrading to a new major version without disrupting production traffic. PostgreSQL releases a new major version annually, MySQL/MariaDB follow their own cadence, and each upgrade brings performance improvements, new features, and security fixes. But upgrading a production database holding terabytes of data is not a trivial task — the wrong approach can mean hours (or days) of downtime.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
