From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Upgrade from 12.22 to 16 |
Date: | 2025-06-11 13:38:53 |
Message-ID: | CANzqJaAg4Tdk-ip-DNr0LLiHkYbDmUb7ZO9Gbi5AX-VdhkyCfw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Jun 11, 2025 at 2:54 AM Wasim Devale <wasimd60(at)gmail(dot)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(dot)albe(at)cybertec(dot)at>
> Date: Wed, 11 Jun, 2025, 12:13 pm
> Subject: Re: Upgrade from 12.22 to 16
> To: Wasim Devale <wasimd60(at)gmail(dot)com>, Pgsql-admin <
> pgsql-admin(at)lists(dot)postgresql(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | Zaid Shabbir | 2025-06-11 15:15:16 | Re: Upgrade from 12.22 to 16 |
Previous Message | Kushal Shri | 2025-06-11 10:54:54 | PostgreSQL Upgrade (v9.5 to v12) with Django 2.0 |