public inbox for [email protected]
help / color / mirror / Atom feedPostgreSQL Upgrade (v9.5 to v12) with Django 2.0
6+ messages / 5 participants
[nested] [flat]
* PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
@ 2025-06-11 10:54 Kushal Shri <[email protected]>
2025-06-12 13:18 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Ron Johnson <[email protected]>
2025-06-12 13:19 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Laurenz Albe <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Kushal Shri @ 2025-06-11 10:54 UTC (permalink / raw)
To: [email protected]
Dear Community,
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.
As part of this, I would like to understand:
- What is the highest PostgreSQL version reliably supported with Django 2.0?
- What upgrade strategies or methods have worked well for you in similar
environments?
- Any gotchas or performance considerations to keep in mind with large
databases during such upgrades?
Your recommendations and experiences will be extremely valuable in helping
us plan and execute this upgrade smoothly.
Thank you in advance for your support!
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
@ 2025-06-12 13:18 ` Ron Johnson <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Ron Johnson @ 2025-06-12 13:18 UTC (permalink / raw)
To: pgsql-admin
--0000000000000a083b06375fc63f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Thu, Jun 12, 2025 at 7:30=E2=80=AFAM Kushal Shri <[email protected]>=
wrote:
> Dear Community,
>
> 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.
>
> As part of this, I would like to understand:
>
> - What is the highest PostgreSQL version reliably supported with Django
> 2.0?
> - What upgrade strategies or methods have worked well for you in similar
> environments?
> - Any gotchas or performance considerations to keep in mind with large
> databases during such upgrades?
>
> Your recommendations and experiences will be extremely valuable in helpin=
g
> us plan and execute this upgrade smoothly.
>
If you have (or can add) 3-4TB on your existing server, then pg_upgrade to
12.22 is possible. (You can also do a hard-links pg_upgrade, but there's
no going back once you start the instance with v12. That's why I like
upgrading to a new disk.) A 3TB instance should take no more than a few
hours (depending on disk and controller speed.)
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
@ 2025-06-12 13:19 ` Laurenz Albe <[email protected]>
2025-06-13 20:14 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Eduardo Barbachan <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Laurenz Albe @ 2025-06-12 13:19 UTC (permalink / raw)
To: Kushal Shri <[email protected]>; [email protected]
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
2025-06-12 13:19 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Laurenz Albe <[email protected]>
@ 2025-06-13 20:14 ` Eduardo Barbachan <[email protected]>
2025-06-15 10:05 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Eduardo Barbachan @ 2025-06-13 20:14 UTC (permalink / raw)
To: Laurenz Albe <[email protected]>; +Cc: Kushal Shri <[email protected]>; [email protected]
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 às 10:19, Laurenz Albe <[email protected]>
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 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
>
>
>
--
Att.
Eduardo Barbachan
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
2025-06-12 13:19 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Laurenz Albe <[email protected]>
2025-06-13 20:14 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Eduardo Barbachan <[email protected]>
@ 2025-06-15 10:05 ` Kushal Shri <[email protected]>
2025-06-22 10:00 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 vrms <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Kushal Shri @ 2025-06-15 10:05 UTC (permalink / raw)
To: [email protected]; [email protected]; +Cc: Laurenz Albe <[email protected]>; [email protected]
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 <
[email protected]> 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 às 10:19, Laurenz Albe <
> [email protected]> 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 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
>>
>>
>>
>
> --
>
> Att.
>
> Eduardo Barbachan
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
2025-06-12 13:19 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Laurenz Albe <[email protected]>
2025-06-13 20:14 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Eduardo Barbachan <[email protected]>
2025-06-15 10:05 ` Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
@ 2025-06-22 10:00 ` vrms <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: vrms @ 2025-06-22 10:00 UTC (permalink / raw)
To: [email protected]
>> if we use the --link option for pg_upgrade, what would be the
rollback plan in case issues arise during or after the upgrade?
restoring a backup would be your option in such a case I guess.
On 15.06.25 12:05, Kushal Shri wrote:
>
> 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
> <[email protected]> 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 às 10:19, Laurenz Albe
> <[email protected]> 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 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
>
>
>
>
> --
>
> Att.
>
> Eduardo Barbachan
>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-06-22 10:00 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-06-11 10:54 PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 Kushal Shri <[email protected]>
2025-06-12 13:18 ` Ron Johnson <[email protected]>
2025-06-12 13:19 ` Laurenz Albe <[email protected]>
2025-06-13 20:14 ` Eduardo Barbachan <[email protected]>
2025-06-15 10:05 ` Kushal Shri <[email protected]>
2025-06-22 10:00 ` vrms <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox