| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(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-18 19:20:59 |
| Message-ID: | 9724B260-8B0E-4B03-A66A-784F792459C9@elevated-dev.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 18, 2024, at 12:10 PM, Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
>
>
> I'd like to add if someone can tolerate some seconds of downtime, with logical replication it is possible to swap the roles of publisher / subscriber so that one can keep the old database as a means of extra safety. If his/her app breaks beyond repair and there is no time for fixing, one can simply go back to the old DB with some minor adjustments (such as sequences).
In the same vein, if one's file system offers atomic snapshots:
1) shut down PG
2) run pg_upgrade with the hard links option
3) take snapshot
4) start up new PG
Now, if there's a failure, you can go back to the snapshot and either start up the old PG, or do some troubleshooting and try upgrading again.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2024-11-18 20:03:03 | Mysterious connections to PostgreSQL (no statement) coming from pgbouncer (mode = transaction) |
| Previous Message | Achilleas Mantzios | 2024-11-18 19:10:47 | Re: Guidance Needed for PostgreSQL Upgrade from 12 to 15 |