From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Ebin Jozer <ebinjozer@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgresql community edition upgrade
Date: Wed, 12 Oct 2022 11:28:45 -0600
Message-ID: <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com> (raw)
In-Reply-To: <CAJuN1jiQ+nUMkay00SSS-axrOBrCL4QoYhRp6sWWdS_S4OHwRg@mail.gmail.com>
References: <CAJuN1jj9=x5FPUypuCGntG82mbZQbW-XOWgbg+H97MrwZ20wLA@mail.gmail.com>
<7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com>
<CAJuN1jiQ+nUMkay00SSS-axrOBrCL4QoYhRp6sWWdS_S4OHwRg@mail.gmail.com>
> On Oct 12, 2022, at 11:18 AM, Ebin Jozer <ebinjozer@gmail.com> wrote:
>
> What would be the rollback step in case the upgrade failed while using pg_upgrade??
- pg_upgrade does pretty extensive pre-flight checks before proceeding
- it does not modify original files, but copies (& modifies the copied catalog files as needed)
(I think even if you use link mode, it doesn't modify original catalog files, so you can start the old one until you have started the new one. I'd look for more info from someone more knowledgeable about this exact process.)
I've personally never seen a problem once the pre-flight passes and it proceeds.
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: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, ebinjozer@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Postgresql community edition upgrade
In-Reply-To: <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox