public inbox for [email protected]  

help / color / mirror / Atom feed

From: Kris Deugau <[email protected]>
To: [email protected]
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Date: Tue, 19 Nov 2024 12:32:29 -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]>

Scott Ribe wrote:
>> On Nov 18, 2024, at 12:10 PM, Achilleas Mantzios <[email protected]> wrote:
>>
>>
>> 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).
> 
> In the same vein, if one's file system offers atomic snapshots:
> 
> 1) shut down PG
> 2) run pg_upgrade with the hard links option
> 3) take snapshot
> 4) start up new PG
> 
> Now, if there's a failure, you can go back to the snapshot and either start up the old PG, or do some troubleshooting and try upgrading again.

Er...  I would think that you'd want to do:

1) shut down PG
2) take snapshot
3) run pg_upgrade with the hard links option
4) start up new PG

as otherwise the old PG won't start properly, due to the changes made by 
pg_upgrade.

-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]
  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