Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 - Mailing list pgsql-admin

From Kris Deugau
Subject Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Date
Msg-id 46c1255a-725f-3f0d-a18f-e1a9c20dd36e@vianet.ca
Whole thread Raw
In response to Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
List pgsql-admin
Scott Ribe wrote:
>> On Nov 19, 2024, at 10:32 AM, Kris Deugau <kdeugau@vianet.ca> 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
toit, you can attempt changes on either the old or new. (Taking care to take additional snapshots as needed, to
preservethe 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



pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Next
From: Scott Ribe
Date:
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15