| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Sameer Malve <malvesameer(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>, Sameer Malve <sameer(dot)malve(at)mobileum(dot)com> |
| Subject: | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |
| Date: | 2024-10-10 06:33:25 |
| Message-ID: | 35e0128148572d2dadfbda0fe748dcac988d3722.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2024-10-10 at 11:52 +0530, Sameer Malve wrote:
> I have few questions.
>
> 1. As I have observed, the PostgreSQL upgrade package has only the lower
> major version binaries. So what if I want to upgrade from PG 13 to PG 16?
That works just the same.
> 2. If upgrade fails then what are the rollback steps. Do you know if it is documented somewhere?
If you didn't use the --link option of pg_upgrade, you can simply fall back to
the old cluster.
If you used --link, you will have to restore your backup (or promote a standby
server that you prepared for this eventuality).
See the pg_upgrade documentation.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SOzcn | 2024-10-10 10:06:40 | Google Cloud PostgreSQL Upgrade v11 to 15 |
| Previous Message | Sameer Malve | 2024-10-10 06:22:47 | Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. |