public inbox for [email protected]
help / color / mirror / Atom feedFrom: Achilleas Mantzios <[email protected]>
To: [email protected]
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Date: Mon, 18 Nov 2024 21:10:47 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaAL-vn0iwP8QGEcVn9RqLv9Uw12qG6fV0h5+AkwW1oGBQ@mail.gmail.com>
References: <CAL5GnisA0RJ=Rd5e6yw4nsCB+DtAS1=iquBKTH76MknnTsHrPg@mail.gmail.com>
<CANzqJaA1VyGqPUQaeT9vfxNV1C3rQJSdMHa9xtzx+rJQhkY2gw@mail.gmail.com>
<CAL5Gnitdyw7vCp4-0whmmJ-RC7Z9yQVx=xrtfQO6-Lxcfvqrqw@mail.gmail.com>
<CANzqJaAL-vn0iwP8QGEcVn9RqLv9Uw12qG6fV0h5+AkwW1oGBQ@mail.gmail.com>
Στις 18/11/24 19:26, ο/η Ron Johnson έγραψε:
> No. Neither rsync nor streaming replication will do version upgrades.
>
> The only ways to do version upgrade are:
> 1. pg_dump + pg_restore
> 2. pg_upgrade
> 3. Logical replication
>
I'd like to add if someone can tolerate some seconds of downtime, with
logical replication it is possible to swap the roles of publisher /
subscriber so that one can keep the old database as a means of extra
safety. If his/her app breaks beyond repair and there is no time for
fixing, one can simply go back to the old DB with some minor adjustments
(such as sequences).
> On Mon, Nov 18, 2024 at 12:20 PM Motog Plus <[email protected]> wrote:
>
> Thanks Ron for your suggestion.
> So for pg upgrade in streaming replication setup, rsync will be a
> better option for standby upgrade if we are using --link option or
> recreating the standby, once upgrade completes on primary? Any
> suggestions on this please.
>
> Best Regards,
> Raman
>
>
> On Mon, Nov 18, 2024, 22:41 Ron Johnson <[email protected]>
> wrote:
>
> On Mon, Nov 18, 2024 at 11:08 AM Motog Plus
> <[email protected]> wrote:
>
> Dear Team,
>
> We are in the process of upgrading our PostgreSQL database
> from version 12 to version 15. I would greatly appreciate
> your advice on the following:
>
> 1. Would it be recommended to use the --link option with
> the pg_upgrade command, from disk space point of view?
>
>
> Yes.
>
> Are there any potential downsides to consider?
>
>
> Very much: it's a one-way journey. No rolling back if
> something goes wrong!
>
> 2. Do you have any suggestions or best practices for
> performing an efficient upgrade in a replication setup
> (streaming replication) for both the primary and standby
> servers?
>
>
> Streaming replication is not an upgrade method. Logical
> replication is absolutely a valid method of upgrading PG on
> one server to PG on a different server.
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
>
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox