| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "Vu Le (JData - HN)" <dba4(at)jprotech(dot)com(dot)vn>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice |
| Date: | 2025-10-11 18:50:16 |
| Message-ID: | aOqm6FaDpWsOSCyo@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Oct 11, 2025 at 08:16:42PM +0200, Laurenz Albe wrote:
> On Sat, 2025-10-11 at 23:02 +0700, Vu Le (JData - HN) wrote:
> > If possible, could you please share any additional best practices or
> > important considerations apart from testing the new version in a
> > staging environment?
>
> All I can think of is:
>
> - Always keep a backup around.
>
> - Read the "Migration to version x" section of the release notes of v14,
> v15, v16 and v17 before you test the application. That will give you
> ideas what areas to test particularly well.
>
> - Test your administrative procedures too. For example, v15 removed
> the exclusive online file system backup.
Agreed, and this might help for reviewing the release notes:
https://momjian.us/main/blogs/pgblog/2022.html#June_13_2022
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-10-11 23:11:18 | Re: Option on `postgres` CLI to shutdown when there are no more active connections? |
| Previous Message | Laurenz Albe | 2025-10-11 18:16:42 | Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice |