<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Python on 3manuek</title><link>https://tr3s.ma/tags/python/</link><description>Recent content in Python on 3manuek</description><language>en-us</language><lastBuildDate>Sat, 15 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://tr3s.ma/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading Postgres Major, and Django model with Logical Replication.</title><link>https://tr3s.ma/posts/2025-11/pgmajorupgradedjango/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://tr3s.ma/posts/2025-11/pgmajorupgradedjango/</guid><description>&lt;h1 id="the-story"&gt;The story&lt;/h1&gt;
&lt;p&gt;A customer needed to upgrade their Aurora RDS Postgres from v13 to v16 due to &lt;strong&gt;v13&amp;rsquo;s EOL&lt;/strong&gt;. This is a common requirement, and so far, a straightforward process.
The complexity arose when they needed to upgrade their application model, which was taking a long time to run due that most of the tables required a full rewrite.&lt;/p&gt;
&lt;p&gt;The Django migration was taking several hours to run, which made a blue/green upgrade and subsequent migration execution unfeasible due to the long downtime it would incur.&lt;/p&gt;</description></item></channel></rss>