public inbox for [email protected]
help / color / mirror / Atom feedFrom: Kris Deugau <[email protected]>
To: Scott Ribe <[email protected]>
Cc: [email protected]
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Date: Tue, 19 Nov 2024 15:40:51 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Scott Ribe wrote:
>> On Nov 19, 2024, at 10:32 AM, Kris Deugau <[email protected]> wrote:
>>
>> as otherwise the old PG won't start properly, due to the changes made by pg_upgrade.
>
> Not true, pg_upgrade leaves it in a state where either can be started. By taking the snapshot after, if you roll back to it, you can attempt changes on either the old or new. (Taking care to take additional snapshots as needed, to preserve the ability to roll back to this state.)
I stand corrected. I hadn't read the docs on pg_upgrade for quite a
while, but after reading the last section in
https://www.postgresql.org/docs/current/pgupgrade.html:
"If you did not start the new cluster, the old cluster was unmodified
except that, when linking started, a .old suffix was appended to
$PGDATA/global/pg_control. To reuse the old cluster, remove the .old
suffix from $PGDATA/global/pg_control; you can then restart the old
cluster."
I see what you mean.
-kgd
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], [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