Downloads
Home   >   mailing lists

Re: Upgrade from 12.22 to 16 - Mailing list pgsql-admin

From Ron Johnson
Subject Re: Upgrade from 12.22 to 16
Date
Msg-id CANzqJaAg4Tdk-ip-DNr0LLiHkYbDmUb7ZO9Gbi5AX-VdhkyCfw@mail.gmail.com
Whole thread Raw
In response to Re: Upgrade from 12.22 to 16  (Wasim Devale <wasimd60@gmail.com>)
List pgsql-admin
Tree view
On Wed, Jun 11, 2025 at 2:54 AM Wasim Devale <wasimd60@gmail.com> wrote:

I mean to say that we do not want to do the in place upgrade

Why not?  Using the default --copy option, there's minimal downtime, and the old database is still there in case you need to fall back, etc.
 

also the other option of taking dump and restoration of it. If I can have any robust plan who all have worked on that then please suggest me.

Thanks,
Wasim


---------- Forwarded message ---------
From: Laurenz Albe <laurenz.albe@cybertec.at>
Date: Wed, 11 Jun, 2025, 12:13 pm
Subject: Re: Upgrade from 12.22 to 16
To: Wasim Devale <wasimd60@gmail.com>, Pgsql-admin <pgsql-admin@lists.postgresql.org>


On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote:
> Please suggest me to upgrade postgresql: 400 GB data with minimal downtime apart
> from in place upgrade. We have it on red hat 9.

What do you mean with "apart from"?

Yours,
Laurenz Albe


--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Kushal Shri
Date:
Subject: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0
Next
From: Ron Johnson
Date:
Subject: Re: PostgreSQL Upgrade (v9.5 to v12) with Django 2.0