MIME-Version: 1.0
From: Jaya Sandeep <jayasandy0909@gmail.com>
Date: Fri, 17 Apr 2026 11:25:11 +0530
Message-ID: <CAEgpDvG76VG4YVq8SayUb+tV2NsB+BfHxE=zBSu+9bxXiChi7Q@mail.gmail.com>
Subject: Guidance Required for PostgreSQL Major Version Upgrade in Pacemaker
 HA Cluster
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000f8be62064fa198c9"
Archived-At: <https://www.postgresql.org/message-id/CAEgpDvG76VG4YVq8SayUb%2BtV2NsB%2BBfHxE%3DzBSu%2B9bxXiChi7Q%40mail.gmail.com>
Precedence: bulk

--000000000000f8be62064fa198c9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=93slave
(primary=E2=80=93standby) 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.


--=20
Regards & Thanks,
Jaya Sandeep
Mobile: +91 94927 27845

--000000000000f8be62064fa198c9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>Dear PostgreSQL Community,</p><p>I am currently plannin=
g a major upgrade of our PostgreSQL environment to the latest stable versio=
n and would appreciate your guidance on the best approach.</p><p>Our curren=
t setup consists of a high-availability cluster managed by Pacemaker on a L=
inux operating system, configured in a master=E2=80=93slave (primary=E2=80=
=93standby) 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.</p><p>I would be grateful=
 if the community could share insights or best practices on the following:<=
/p><ul><li><p>Recommended upgrade strategy (in-place upgrade vs. logical re=
plication vs. dump/restore) for a Pacemaker-managed HA cluster</p></li><li>=
<p>Handling failover and cluster resources during the upgrade process</p></=
li><li><p>Any precautions or common pitfalls specific to Pacemaker-based Po=
stgreSQL clusters</p></li><li><p>Suggested sequence of steps to ensure a sm=
ooth and safe transition</p></li></ul><div><b>Details :</b></div><div>Curre=
nt version of PostgreSQL is <b>14.6=C2=A0</b></div><div>OS: Linux=C2=A0</di=
v><div>HA :Pacemaker Based=C2=A0</div><div>Master -Slave=C2=A0 --Setup</div=
><div><br></div><div>If anyone has experience performing a similar upgrade =
or can point me to relevant documentation or case studies, that would be ex=
tremely helpful.</div><p>Thank you in advance for your support.</p><p><br><=
/p><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" cl=
ass=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"=
>Regards &amp; Thanks,<br>Jaya Sandeep<br>Mobile: +91 94927 27845<br><table=
 cellpadding=3D"0" style=3D"width:479.259px"><tbody><tr><td style=3D"width:=
476.296px"><div></div></td></tr></tbody></table></div></div></div>

--000000000000f8be62064fa198c9--