Re: v11.5- v15.3 upgrade (linux) - Mailing list pgsql-general

From Yogesh Sharma
Subject Re: v11.5- v15.3 upgrade (linux)
Date
Msg-id 88132f81-7e82-4d53-a55a-eede564351da@catprosystems.com
Whole thread Raw
In response to v11.5- v15.3 upgrade (linux)  (David Gauthier <dfgpostgres@gmail.com>)
Responses Re: v11.5- v15.3 upgrade (linux)  (David Gauthier <dfgpostgres@gmail.com>)
List pgsql-general
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




pgsql-general by date:

Previous
From: David Gauthier
Date:
Subject: creating a subset DB efficiently ?
Next
From: David Gauthier
Date:
Subject: Re: v11.5- v15.3 upgrade (linux)