MIME-Version: 1.0
References: <CAJ4rSwspyYBppQS701C=BVFX2yrP1JErgDCZXbC15BQh2zAS1Q@mail.gmail.com>
 <CAKAnmmK47O_rYDB4iPe=K3QiqzJcCnnxCoYs_40Q1YWb=x0nDg@mail.gmail.com> <CAJ4rSwvsRJhwfuem0vsws1WwRZPN8Ju2Nw0e0Oc2j7n=MXUhMg@mail.gmail.com>
In-Reply-To: <CAJ4rSwvsRJhwfuem0vsws1WwRZPN8Ju2Nw0e0Oc2j7n=MXUhMg@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 24 Oct 2025 08:58:57 -0400
Message-ID: <CAKAnmm+DcNS_FTGOG9Q3WUQGxxukhqf1rz5jrqzAk0z9W5d59A@mail.gmail.com>
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9
 (PostgreSQL 11 streaming replication)
To: Bala M <krishna.pgdba@gmail.com>
Cc: "adrian.klaver@aklaver.com" <adrian.klaver@aklaver.com>, chris+google@qwirx.com, 
	pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000cb847b0641e71e0d"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BDcNS_FTGOG9Q3WUQGxxukhqf1rz5jrqzAk0z9W5d59A%40mail.gmail.com>
Precedence: bulk

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

On Thu, Oct 23, 2025 at 10:51=E2=80=AFAM Bala M <krishna.pgdba@gmail.com> w=
rote:

> Any advice, recommendations, or shared experiences from others who have
> performed similar migrations would be greatly appreciated.


Some related advice: put some system in place to make sure you are always
running the latest revision in whatever major version you end up. See:

https://www.postgresql.org/support/versioning/

In particular, note this part:

*The community considers performing minor upgrades to be less risky than
continuing to run an old minor version.*

You also want to put something in place to make sure your major version
does not  fall so far behind again. You don't need to upgrade every year,
but certainly target a major upgrade every 2-3 years. As you will discover,
the major upgrade process is going to be much easier than this current
upgrade we are talking about in this thread.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Oct 23, 2025 at 10:51=E2=80=AFAM =
Bala M &lt;<a href=3D"mailto:krishna.pgdba@gmail.com">krishna.pgdba@gmail.c=
om</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">An=
y advice, recommendations, or shared experiences from others who have perfo=
rmed similar migrations would be greatly appreciated.</blockquote><div clas=
s=3D"gmail_quote gmail_quote_container"><div><br></div></div><div dir=3D"lt=
r" class=3D"gmail_signature"><div dir=3D"ltr"><div>Some related advice: put=
 some system in place to make sure you are always running the latest revisi=
on in whatever major version you end up. See:</div><div><br></div><div><a h=
ref=3D"https://www.postgresql.org/support/versioning/">https://www.postgres=
ql.org/support/versioning/</a></div><div><br></div><div>In particular, note=
 this part:</div><div><br></div><div><em style=3D"box-sizing:border-box;col=
or:rgb(0,0,0);font-size:15.3333px"><font face=3D"monospace">The community c=
onsiders performing minor upgrades to be less risky than continuing to run =
an old minor version.</font></em></div><div><br></div><div>You also want to=
 put something in place to make sure your major version does not=C2=A0 fall=
 so far behind again. You don&#39;t need to upgrade every year, but certain=
ly target a major upgrade every 2-3 years. As you will discover, the major =
upgrade process is going to be much easier than this current upgrade we are=
 talking about in this thread.</div><div><br></div><div>Cheers,</div><div>G=
reg</div><div><br></div><div>--</div><div>Crunchy Data - <a href=3D"https:/=
/www.crunchydata.com" target=3D"_blank">https://www.crunchydata.com</a></di=
v><div>Enterprise Postgres Software Products &amp; Tech Support</div><div><=
br></div></div></div></div>

--000000000000cb847b0641e71e0d--