From: | Johnathan Tiamoh <johnathantiamoh(at)gmail(dot)com> |
---|---|
To: | Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Safest pgupgrade jump distance |
Date: | 2024-02-12 13:31:02 |
Message-ID: | CACoPQdYEcUYWT1OVsTHdg-Kb96AR1gP21pxJfEwusoaht0z9bg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have upgraded from 9.5 to 14 using the -link option. It works fine.
I equally had streaming replication running on it.
I break(split brain) replication and upgrade the standby, once it done and
everything is running smoothly, I then install version 14 to the old
primary and just configure streaming on it and all now runs on 14.
On Mon, Feb 12, 2024 at 5:08 AM Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com>
wrote:
> Hi, I was wondering what is the safest pg_upgrade version upgrade distance
> going from 9.6 version. Do I need to go version by version or I can go from
> 9.6 to 15? We have a very huge database(TBs) with one replication server,
> so we will first run the pgupgrade on the main server and then rsync to a
> standby replica. I'm not sure whether it's safe to do it from 9.6 to 15 at
> once, I have tested the process on 9,6 to 10 yet. Would that be a wise
> approach to such an upgrade of the db?
> Also, when upgrading a very big database with replication where none of
> the data can be allowed to be lost, is the pgupgrade into rsync approach
> the best one? Thanks.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-02-12 14:31:50 | Re: Safest pgupgrade jump distance |
Previous Message | Dominique Devienne | 2024-02-12 10:30:09 | Re: How to do faster DML |