MIME-Version: 1.0
References: 
 <CANzqJaCNaqhQ9duPP+eKU2OR1wjGYW-FBQ2FZXqnBRb6XAnKQA@mail.gmail.com>
 <26493.1779468779@sss.pgh.pa.us>
 <CANzqJaCJGS9S=ibJ_rOmP=acA7n0XCA5R4FbMH+AH3WURhey8Q@mail.gmail.com>
 <7eb3ea21-5bf9-42bd-ac11-0fdc6f48866d@jakobs.com>
 <CANzqJaAb149k3pYmbnZ8-Mcc7Ec_DwJMkKiZK=tPA34Rsq_kDw@mail.gmail.com>
In-Reply-To: 
 <CANzqJaAb149k3pYmbnZ8-Mcc7Ec_DwJMkKiZK=tPA34Rsq_kDw@mail.gmail.com>
From: Ramakrishna Reddy Nandyala <rkreddy.n@gmail.com>
Date: Wed, 3 Jun 2026 17:44:39 +0530
Message-ID: 
 <CA++_dZP4ygDekyvxmYbM8=egGshB4CRAd1mBHrdusO3CXzYwuw@mail.gmail.com>
Subject: Any known bugs with respect to data corruption in pg12/pg 14
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000db07ca0653585f89"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2B%2B_dZP4ygDekyvxmYbM8%3DegGshB4CRAd1mBHrdusO3CXzYwuw%40mail.gmail.com>
Precedence: bulk

--000000000000db07ca0653585f89
Content-Type: text/plain; charset="UTF-8"

Hi Gurus

We are facing a peculiar issue with respect to pg 12 and pg14 on
RHEL8u10,post os patch objects are getting corrupted. The details are
unknown until we access the object's.
System Stack:

 Db: pg12.22,pg14.19
Os : Rhel 8u10
THALES CTM FOR encryption solution
Stirage : Pure storage and VSAN DISK

We are not seeing any errors reported with respect to the corruption,unless
until we select The problematic object that to the problematic block only

Below corruption scenarios we observed
1) if the corruption happen on standby node no impact to the production
2) if corruption happen on production we could see same object we are
unable to select from standby node,means corruption is transfer to standby
node
3) if the corruption happen on block 0 it is not allowing to perform any
DML activity,if it is on other blocks it is allowing to
insert/update/delete in other good blocks,if system touches the problematic
block only it is failing


Need your guide lines how to identify what is going wrong,and where is
going wrong?

Is there any known bugs in these version with the given stack pg12/14 with
RHEL8u10

Is there any way we can stop not to replicate the problematic block to
standby node?

What will be the best practice to identify the problematic objects or blocks

We tried amcheck on pg14 it is not giving any results

Your expertise advise will be help us on coming out of the critical issue

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

Hi Gurus<div dir=3D"auto"><br></div><div dir=3D"auto">We are facing a pecul=
iar issue with respect to pg 12 and pg14 on RHEL8u10,post os patch objects =
are getting corrupted. The details are unknown until we access the object&#=
39;s.=C2=A0</div><div dir=3D"auto">System Stack:</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">=C2=A0Db: pg12.22,pg14.19</div><div dir=3D"auto">O=
s : Rhel 8u10</div><div dir=3D"auto">THALES CTM FOR encryption solution</di=
v><div dir=3D"auto">Stirage : Pure storage and VSAN DISK=C2=A0</div><div di=
r=3D"auto"><br></div><div dir=3D"auto">We are not seeing any errors reporte=
d with respect to the corruption,unless until we select The problematic obj=
ect that to the problematic block only</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Below corruption scenarios we observed</div><div dir=3D"auto=
">1) if the corruption happen on standby node no impact to the production=
=C2=A0</div><div dir=3D"auto">2) if corruption happen on production we coul=
d see same object we are unable to select from standby node,means corruptio=
n is transfer to standby node</div><div dir=3D"auto">3) if the corruption h=
appen on block 0 it is not allowing to perform any DML activity,if it is on=
 other blocks it is allowing to insert/update/delete in other good blocks,i=
f system touches the problematic block only it is failing</div><div dir=3D"=
auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Need your gui=
de lines how to identify what is going wrong,and where is going wrong?</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">Is there any known bugs in t=
hese version with the given stack pg12/14 with RHEL8u10</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Is there any way we can stop not to replica=
te the problematic block to standby node?</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">What will be the best practice to identify the problemati=
c objects or blocks</div><div dir=3D"auto"><br></div><div dir=3D"auto">We t=
ried amcheck on pg14 it is not giving any results</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Your expertise advise will be help us on coming o=
ut of the critical issue=C2=A0</div><div dir=3D"auto"><br></div>

--000000000000db07ca0653585f89--