Request a Demo
Home   >   mailing lists

Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice
Date
Msg-id aOqm6FaDpWsOSCyo@momjian.us
Whole thread Raw
In response to Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice
List pgsql-general
Tree view 
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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice
Next
From: Adrian Klaver
Date:
Subject: Re: Option on `postgres` CLI to shutdown when there are no more active connections?