| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Kris Deugau <kdeugau(at)vianet(dot)ca> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 |
| Date: | 2024-11-19 21:16:47 |
| Message-ID: | 5720FA08-368D-4A8C-B160-A104D08C829B@elevated-dev.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 19, 2024, at 1:40 PM, Kris Deugau <kdeugau(at)vianet(dot)ca> wrote:
>
> 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.
>
There's nothing wrong per se about taking the snapshot before, I was just saving the potential time of re-running pg_upgrade. Heck, take a snapshot before *and* after ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Srini Genji | 2024-11-21 00:06:05 | Disable Save results to file button |
| Previous Message | Kris Deugau | 2024-11-19 20:40:51 | Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 |