Message-ID: <cae2772d1d0d441aa48ac410409c83d64f1d3ede.camel@cybertec.at>
Subject: Re: Upgrade & Rollback plan: My customer requests rollback via
 old-version standby (13 =?UTF-8?Q?=E2=86=94?= 17) =?UTF-8?Q?=E2=80=94?=
 need community advice
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "Vu Le (JData - HN)" <dba4@jprotech.com.vn>
Cc: pgsql-general@lists.postgresql.org
Date: Sat, 11 Oct 2025 20:16:42 +0200
In-Reply-To: <CACT9sojZgGUtpm64dqdAf5pRrBgxxsweMcR7mZFmmnoOjoRApw@mail.gmail.com>
References: 
	<CACT9sogdbwVqsXQeT-V8GP+GhhQrQcwmCPOCTtaPL35jHg5UXQ@mail.gmail.com>
	 <8b4a6869b1fca2d0c39777b76439e6f153ba8c76.camel@cybertec.at>
	 <CACT9sojZgGUtpm64dqdAf5pRrBgxxsweMcR7mZFmmnoOjoRApw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/cae2772d1d0d441aa48ac410409c83d64f1d3ede.camel%40cybertec.at>
Precedence: bulk

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.

Yours,
Laurenz Albe