MIME-Version: 1.0
References: <CAJ4rSwspyYBppQS701C=BVFX2yrP1JErgDCZXbC15BQh2zAS1Q@mail.gmail.com>
In-Reply-To: <CAJ4rSwspyYBppQS701C=BVFX2yrP1JErgDCZXbC15BQh2zAS1Q@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 22 Oct 2025 13:35:12 -0400
Message-ID: <CAKAnmmK47O_rYDB4iPe=K3QiqzJcCnnxCoYs_40Q1YWb=x0nDg@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: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000471ba20641c2bf49"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmK47O_rYDB4iPe%3DK3QiqzJcCnnxCoYs_40Q1YWb%3Dx0nDg%40mail.gmail.com>
Precedence: bulk

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

On Wed, Oct 22, 2025 at 6:53=E2=80=AFAM Bala M <krishna.pgdba@gmail.com> wr=
ote:

>
>    -
>
>    PostgreSQL Version: 11.15
>
>
Ouch! Not only is the major version end of life, but that's not even the
latest revision of 11. At this point, you should use logical replication to
migrate from your v11 to a shiny new Postgres v18 on your RHEL9 box. As
Chris pointed out, the indexes are a libc problem, but your bigger problem
is being on v11.15. If you want to trade complexity for time, you could
consider using pg_dump to do the upgrade instead of logical replication.


Cheers,
Greg

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Oct 22, 2025 at 6:53=E2=80=AFAM B=
ala M &lt;<a href=3D"mailto:krishna.pgdba@gmail.com">krishna.pgdba@gmail.co=
m</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><ul><li=
><p>PostgreSQL Version: 11.15</p></li></ul></div></div></blockquote><div><b=
r></div><div>Ouch! Not only is the major version end of life, but that&#39;=
s not even the latest revision of 11. At this point, you should use logical=
 replication to migrate from your v11 to a shiny new Postgres v18 on your R=
HEL9 box. As Chris pointed out, the indexes are a libc problem, but your bi=
gger problem is being on v11.15. If you want to trade complexity for time, =
you could consider using pg_dump to do the upgrade instead of logical repli=
cation.</div><div><br></div><div><br></div></div><div dir=3D"ltr" class=3D"=
gmail_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br=
></div><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata.=
com" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterprise=
 Postgres Software Products &amp; Tech Support</div><div><br></div></div></=
div></div>

--000000000000471ba20641c2bf49--