public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Kushal Shri <[email protected]>
To: [email protected]
Subject: Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
Date: Thu, 12 Jun 2025 15:19:37 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMSJNCXWkhYQ=YwSt+SQLT710+8KL3rRyb7Wo-fUerbr5o3idg@mail.gmail.com>
References: <CAMSJNCXWkhYQ=YwSt+SQLT710+8KL3rRyb7Wo-fUerbr5o3idg@mail.gmail.com>
On Wed, 2025-06-11 at 16:39 +0545, Kushal Shri wrote:
> We are in the process of planning a PostgreSQL upgrade and would greatly
> appreciate any insights, best practices, or lessons learned from your experiences.
>
> Current Setup:
> - PostgreSQL version: 9.5
> - Django version: 2.0
> - Database size: ~3 TB
> - One Master 4 Replicas(Streaming Replication)
>
> We are taking a phased approach to this upgrade. In Phase 1, our goal is to
> upgrade PostgreSQL from v9.5 to v12, ensuring compatibility with our current
> Django 2.0 application.
That's already wrong. PostgreSQL v12 is out of support. Upgrade to v17 or v18.
> As part of this, I would like to understand:
>
> - What is the highest PostgreSQL version reliably supported with Django 2.0?
You'll have to ask Django what they support.
> - What upgrade strategies or methods have worked well for you in similar environments?
pg_upgrade --link
> - Any gotchas or performance considerations to keep in mind with large databases
> during such upgrades?
Make sure you don't have millions of Large Objects, otherwise the upgrade
will be very slow and memory consuming.
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox