pgsql-general
❮
Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker HA Cluster
- Jump to comment-1Jaya Sandeep<jayasandy0909@gmail.com>Apr 17, 2026, 5:59 AM UTCDear PostgreSQL Community,
I am currently planning a major upgrade of our PostgreSQL environment to
the latest stable version and would appreciate your guidance on the best
approach.
Our current setup consists of a high-availability cluster managed by
Pacemaker on a Linux operating system, configured in a master–slave
(primary–standby) architecture. Given the critical nature of this
environment, we want to ensure the upgrade is performed with minimal
downtime and without compromising data integrity or cluster stability.
I would be grateful if the community could share insights or best practices
on the following:
Details :- Recommended upgrade strategy (in-place upgrade vs. logical replication vs. dump/restore) for a Pacemaker-managed HA cluster - Handling failover and cluster resources during the upgrade process - Any precautions or common pitfalls specific to Pacemaker-based PostgreSQL clusters - Suggested sequence of steps to ensure a smooth and safe transition
Current version of PostgreSQL is 14.6
OS: Linux
HA :Pacemaker Based
Master -Slave --Setup
If anyone has experience performing a similar upgrade or can point me to
relevant documentation or case studies, that would be extremely helpful.
Thank you in advance for your support.
--
Regards & Thanks,
Jaya Sandeep
Mobile: +91 94927 27845- Jump to comment-1Ron Johnson<ronljohnsonjr@gmail.com>Apr 17, 2026, 1:13 PM UTCOn Fri, Apr 17, 2026 at 1:55 AM Jaya Sandeep <jayasandy0909@gmail.com>
wrote:
[snip]Details :
Step #1 is to update to fix the 3.5 years of bugs from 14.6 to 14.22. Each
Current version of PostgreSQL is 14.6
node update should take no more than 5 minutes.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!- Jump to comment-1Jaya Sandeep<jayasandy0909@gmail.com>Apr 17, 2026, 1:20 PM UTCUpgrading to 16 version, guidance on this .
Thank you.
Regards,
Neelam Jaya Sandeep
9492727845
On Fri, 17 Apr, 2026, 18:43 Ron Johnson, <ronljohnsonjr@gmail.com> wrote:On Fri, Apr 17, 2026 at 1:55 AM Jaya Sandeep <jayasandy0909@gmail.com>
wrote:
[snip]Details :
Current version of PostgreSQL is 14.6
Step #1 is to update to fix the 3.5 years of bugs from 14.6 to 14.22.
Each node update should take no more than 5 minutes.
--Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
- Jump to comment-1Adrian Klaver<adrian.klaver@aklaver.com>Apr 17, 2026, 2:08 PM UTCOn 4/17/26 6:20 AM, Jaya Sandeep wrote:
Upgrading to 16 version, guidance on this .
Ron's point is that you are currently at Postgres 14.6 and there are approximately 4 years of bug fixes to the current stable 14.22 version as seen here:
https://www.postgresql.org/docs/14/release.html
It would be good idea to bring the 14 instance to as an up to date state as possible before moving on to latest major version(18), which in itself is a jump of 4 major versions.
As to the major to major upgrade I would suggest reading:
https://clusterlabs.org/projects/pacemaker/doc/3.0/Pacemaker_Administration/html/
and
https://www.postgresql.org/docs/18/pgupgrade.htmlThank you.
Regards,Neelam Jaya Sandeep
9492727845On Fri, 17 Apr, 2026, 18:43 Ron Johnson, <ronljohnsonjr@gmail.com > <mailto:ronljohnsonjr@gmail.com>> wrote:
On Fri, Apr 17, 2026 at 1:55 AM Jaya Sandeep
<jayasandy0909@gmail.com <mailto:jayasandy0909@gmail.com>> wrote:
[snip]
Details :
Current version of PostgreSQL is 14.6
Step #1 is to update to fix the 3.5 years of bugs from 14.6 to
14.22. Each node update should take no more than 5 minutes.
-- > Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
-- Adrian Klaver
adrian.klaver@aklaver.com- Jump to comment-1Adrian Klaver<adrian.klaver@aklaver.com>Apr 17, 2026, 2:19 PM UTCOn 4/17/26 7:08 AM, Adrian Klaver wrote:
On 4/17/26 6:20 AM, Jaya Sandeep wrote:
Upgrading to 16 version, guidance on this .
Ron's point is that you are currently at Postgres 14.6 and there are > approximately 4 years of bug fixes to the current stable 14.22 version > as seen here:
https://www.postgresql.org/docs/14/release.html
It would be good idea to bring the 14 instance to as an up to date state > as possible before moving on to latest major version(18), which in > itself is a jump of 4 major versions.
Forgot to add to previous post. As you are changing the major version you should go the Release Notes section for each major version(15-18) and read through the notes for the changes that may affect you. It is generally sufficient to look at just the initial release for each major version as that where the new/breaking features are called out. Ideally you would set up a test instance and verify that your code works in the Postgres major version you wish to migrate to.As to the major to major upgrade I would suggest reading:
https://clusterlabs.org/projects/pacemaker/doc/3.0/ > Pacemaker_Administration/html/
and
https://www.postgresql.org/docs/18/pgupgrade.htmlThank you.
Regards,
Neelam Jaya Sandeep
9492727845On Fri, 17 Apr, 2026, 18:43 Ron Johnson, <ronljohnsonjr@gmail.com >> <mailto:ronljohnsonjr@gmail.com>> wrote:
On Fri, Apr 17, 2026 at 1:55 AM Jaya Sandeep<jayasandy0909@gmail.com <mailto:jayasandy0909@gmail.com>> wrote:
[snip]
Details :
Current version of PostgreSQL is 14.6
Step #1 is to update to fix the 3.5 years of bugs from 14.6 to
14.22. Each node update should take no more than 5 minutes.-- Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
adrian.klaver@aklaver.com
-- Adrian Klaver