From: Yogesh Sharma <yogesh.sharma@catprosystems.com>
To: David Gauthier <dfgpostgres@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: v11.5- v15.3 upgrade (linux)
Date: Fri, 8 Mar 2024 11:28:20 -0500
Message-ID: <88132f81-7e82-4d53-a55a-eede564351da@catprosystems.com> (raw)
In-Reply-To: <CAEs=6D=T+eAj7GJZiNz6_o60OqAYmy4xd9jJ1tbqcp+X17etPA@mail.gmail.com>
References: <CAEs=6D=T+eAj7GJZiNz6_o60OqAYmy4xd9jJ1tbqcp+X17etPA@mail.gmail.com>
Greetings,
On 3/6/24 19:19, David Gauthier wrote:
> Hi:
> I'm a PG user in a big corp with an IT dept that administers a PG
> server/instance that I use. It's an old install, v11.5, and we need
> to upgrade to v15.3. They want to bring the upgraded DB up on a new
> linux vm which has OS upgrades of its own. So it's a move AND an
> upgrade. There are 2 concerns....
>
> First has to do with a jump from 11.5 - 15.3 ? Is it safe to do this
> given so many major intermediate versions being skipped ?
Generally speaking, it is safe from database point of view but you have
to verify that application is working as expected with PostgreSQL 15,
driver update, any query performance issues, any deprecate features in
use, collation differences, and performance verification, etc.
PostgreSQL supports dump/restore (slow and longer downtime), binary
upgrade using pg_upgrade (faster and low downtime), and logical
replication (complex and least downtime). Since OS upgrade is also part
of the equation, dump/restore or logical are better candidates. Due to
OS collation difference I would avoid binary upgrade path.
--
Kind Regards,
Yogesh Sharma
PostgreSQL, Linux, and Networking Expert
Open Source Enthusiast and Advocate
PostgreSQL Contributors Team @ RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: yogesh.sharma@catprosystems.com, dfgpostgres@gmail.com
Subject: Re: v11.5- v15.3 upgrade (linux)
In-Reply-To: <88132f81-7e82-4d53-a55a-eede564351da@catprosystems.com>
References: <CAEs=6D=T+eAj7GJZiNz6_o60OqAYmy4xd9jJ1tbqcp+X17etPA@mail.gmail.com> <88132f81-7e82-4d53-a55a-eede564351da@catprosystems.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox