Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Kushal Shri <shrikushalk(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
Date: 2025-06-12 13:19:37
Message-ID: 61b6cfb6ae03b5ad6512d0d167a5cb409ae58f21.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Eduardo Barbachan 2025-06-13 20:14:17 Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
Previous Message Ron Johnson 2025-06-12 13:18:52 Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0