Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: Postgresql community edition upgrade
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAJuN1jiQ+nUMkay00SSS-axrOBrCL4QoYhRp6sWWdS_S4OHwRg@mail.gmail.com>
Date: Wed, 12 Oct 2022 11:28:45 -0600
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com>
References: 
 <CAJuN1jj9=x5FPUypuCGntG82mbZQbW-XOWgbg+H97MrwZ20wLA@mail.gmail.com>
 <7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com>
 <CAJuN1jiQ+nUMkay00SSS-axrOBrCL4QoYhRp6sWWdS_S4OHwRg@mail.gmail.com>
To: Ebin Jozer <ebinjozer@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/9571D051-5B4F-45FB-A52B-9D84C601B7DC%40elevated-dev.com>
Precedence: bulk

> On Oct 12, 2022, at 11:18 AM, Ebin Jozer <ebinjozer@gmail.com> wrote:
>=20
> 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.=