<?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 Mohammad Aziz</title>
    <link>https://iaziz786.com/tags/upgrade/</link>
    <description>Recent content in Upgrade on Mohammad Aziz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 21 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iaziz786.com/tags/upgrade/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What breaks in PostgreSQL 19, and how to check before you upgrade</title>
      <link>https://iaziz786.com/blog/upgrading-to-postgresql-19/</link>
      <pubDate>Sat, 21 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://iaziz786.com/blog/upgrading-to-postgresql-19/</guid>
      <description>PostgreSQL 19 was released on November 19, 2026. If you run Postgres in production, the binary upgrade path from 18 looks familiar. You install the new binaries, create a new cluster, and run pg_upgrade.&#xA;The failures are less obvious. Some come from catalog objects that pg_upgrade inspects. Others come from settings and defaults that it does not read. This post separates the two. It covers the blockers that pg_upgrade --check reports before you touch data, an experiment that shows the most likely one, and the changes that pass the check and still cause problems after the upgrade.</description>
    </item>
  </channel>
</rss>
