MIME-Version: 1.0
References: 
 <CAMSJNCXWkhYQ=YwSt+SQLT710+8KL3rRyb7Wo-fUerbr5o3idg@mail.gmail.com>
 <61b6cfb6ae03b5ad6512d0d167a5cb409ae58f21.camel@cybertec.at>
 <CAGEDDz-9uaYihyW5hWYXj2XU+4khxQx+S9yJk5pnf-=+brMueA@mail.gmail.com>
In-Reply-To: 
 <CAGEDDz-9uaYihyW5hWYXj2XU+4khxQx+S9yJk5pnf-=+brMueA@mail.gmail.com>
From: Kushal Shri <shrikushalk@gmail.com>
Date: Sun, 15 Jun 2025 15:50:27 +0545
Message-ID: 
 <CAMSJNCVfYATtRBkjAP-egVcP_sepTSEp9=_YLf5EL4Z0L0B4HA@mail.gmail.com>
Subject: Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
To: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, eduardobarbachandb@gmail.com
Content-Type: multipart/alternative; boundary="000000000000d0281c0637996be4"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMSJNCVfYATtRBkjAP-egVcP_sepTSEp9%3D_YLf5EL4Z0L0B4HA%40mail.gmail.com>
Precedence: bulk

--000000000000d0281c0637996be4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Currently, our plan is to test pg_upgrade using the --link option to
upgrade from PostgreSQL 9.5 to 12, then upgrade Django to the latest
supported version, and finally perform another pg_upgrade to PostgreSQL 16.

Since Django 2.0 is officially tested and supported only up to PostgreSQL
10, would you recommend upgrading to PostgreSQL 10 using pg_upgrade as the
first phase, followed by logical replication to PostgreSQL 16 as the final
target after upgrading Django as well?

and, if we use the --link option for pg_upgrade, what would be the rollback
plan in case issues arise during or after the upgrade?


On Sat, 14 Jun 2025 at 01:59, Eduardo Barbachan <
eduardobarbachandb@gmail.com> wrote:

> I'm sorry if this part of the answer should not be given in this context,
> but I happen to be in this list (as a lurker for most of the time) and be=
 a
> Django user.
> Till Django 4.2 (LTS) postgres 12 is supported. Django 5.2 (LTS also)
> supports postgres 17+.
>
>
> Em qui., 12 de jun. de 2025 =C3=A0s 10:19, Laurenz Albe <
> laurenz.albe@cybertec.at> escreveu:
>
>> On Wed, 2025-06-11 at 16:39 +0545, Kushal Shri wrote:
>> > We are in the process of planning a PostgreSQL upgrade and would great=
ly
>> > 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 Djang=
o
>> 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 upgrad=
e
>> will be very slow and memory consuming.
>>
>> Yours,
>> Laurenz Albe
>>
>>
>>
>
> --
>
> Att.
>
> Eduardo  Barbachan
>

--000000000000d0281c0637996be4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Currently, our plan is to test pg_upgrade using the --l=
ink option to upgrade from PostgreSQL 9.5 to 12, then upgrade Django to the=
 latest supported version, and finally perform another pg_upgrade to Postgr=
eSQL 16.</p><p></p><p>Since Django 2.0 is officially tested and supported o=
nly up to PostgreSQL 10, would you recommend upgrading to PostgreSQL 10 usi=
ng pg_upgrade as the first phase, followed by logical replication to Postgr=
eSQL 16 as the final target after upgrading Django as well?</p><p></p><p>an=
d, if we use the --link option for pg_upgrade, what would be the rollback p=
lan in case issues arise during or after the upgrade?</p><p></p></div><br><=
div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"g=
mail_attr">On Sat, 14 Jun 2025 at 01:59, Eduardo Barbachan &lt;<a href=3D"m=
ailto:eduardobarbachandb@gmail.com">eduardobarbachandb@gmail.com</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div>I&#39;m sorry if this part of the answer should not be given in =
this context, but I happen to be in this list (as a lurker for most of the =
time) and be a Django user.=C2=A0<br>Till Django 4.2 (LTS) postgres 12 is s=
upported. Django 5.2 (LTS also) supports postgres 17+.</div><div><br></div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
Em qui., 12 de jun. de 2025 =C3=A0s 10:19, Laurenz Albe &lt;<a href=3D"mail=
to:laurenz.albe@cybertec.at" target=3D"_blank">laurenz.albe@cybertec.at</a>=
&gt; escreveu:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">O=
n Wed, 2025-06-11 at 16:39 +0545, Kushal Shri wrote:<br>
&gt; We are in the process of planning a PostgreSQL upgrade and would great=
ly<br>
&gt; appreciate any insights, best practices, or lessons learned from your =
experiences.<br>
&gt; <br>
&gt; Current Setup:<br>
&gt; =C2=A0 =C2=A0- PostgreSQL version: 9.5<br>
&gt; =C2=A0 =C2=A0- Django version: 2.0<br>
&gt; =C2=A0 =C2=A0- Database size: ~3 TB<br>
&gt; =C2=A0 =C2=A0- One Master 4 Replicas(Streaming Replication)<br>
&gt; <br>
&gt; We are taking a phased approach to this upgrade. In Phase 1, our goal =
is to<br>
&gt; upgrade PostgreSQL from v9.5 to v12, ensuring compatibility with our c=
urrent<br>
&gt; Django 2.0 application.<br>
<br>
That&#39;s already wrong.=C2=A0 PostgreSQL v12 is out of support.=C2=A0 Upg=
rade to v17 or v18.<br>
<br>
&gt; As part of this, I would like to understand:<br>
&gt; <br>
&gt; - What is the highest PostgreSQL version reliably supported with Djang=
o 2.0?<br>
<br>
You&#39;ll have to ask Django what they support.<br>
<br>
&gt; - What upgrade strategies or methods have worked well for you in simil=
ar environments?<br>
<br>
pg_upgrade --link<br>
<br>
&gt; - Any gotchas or performance considerations to keep in mind with large=
 databases<br>
&gt;=C2=A0 =C2=A0during such upgrades?<br>
<br>
Make sure you don&#39;t have millions of Large Objects, otherwise the upgra=
de<br>
will be very slow and memory consuming.<br>
<br>
Yours,<br>
Laurenz Albe<br>
<br>
<br>
</blockquote></div><div><br clear=3D"all"></div><br><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr"><div><div dir=3D"ltr"><div><p style=3D"margin-bottom:12pt">A=
tt.</p><p>Eduardo =C2=A0Barbachan<br></p></div></div></div></div></div>
</blockquote></div>

--000000000000d0281c0637996be4--