Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15

From: Kris Deugau <kdeugau(at)vianet(dot)ca>
To: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Date: 2024-11-19 20:40:51
Message-ID: 46c1255a-725f-3f0d-a18f-e1a9c20dd36e@vianet.ca
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Scott Ribe wrote:
>> On Nov 19, 2024, at 10:32 AM, Kris Deugau <kdeugau(at)vianet(dot)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 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2024-11-19 21:16:47 Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15
Previous Message Scott Ribe 2024-11-19 17:42:42 Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15