public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jaya Sandeep <[email protected]>
To: [email protected]
Subject: Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker HA Cluster
Date: Fri, 17 Apr 2026 11:25:11 +0530
Message-ID: <CAEgpDvG76VG4YVq8SayUb+tV2NsB+BfHxE=zBSu+9bxXiChi7Q@mail.gmail.com> (raw)
Dear 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:
-
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
*Details :*
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
reply
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker HA Cluster
In-Reply-To: <CAEgpDvG76VG4YVq8SayUb+tV2NsB+BfHxE=zBSu+9bxXiChi7Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox