| From: | Jaya Sandeep <jayasandy0909(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker HA Cluster |
| Date: | 2026-04-17 05:55:11 |
| Message-ID: | CAEgpDvG76VG4YVq8SayUb+tV2NsB+BfHxE=zBSu+9bxXiChi7Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-04-17 13:13:09 | Re: Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker HA Cluster |
| Previous Message | Dutch Glory | 2026-04-17 02:50:29 | postgresql19-server-19-alpha sles 15.7 still needs older Leap 15.6 Packages . |