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>
 <CA++_dZP4ygDekyvxmYbM8=egGshB4CRAd1mBHrdusO3CXzYwuw@mail.gmail.com>
 <CAM=sWa4JmWhMzpJRyVdFw5h+gjE9Q3RoOrhQW2Rx7pN02_6bzA@mail.gmail.com>
In-Reply-To: 
 <CAM=sWa4JmWhMzpJRyVdFw5h+gjE9Q3RoOrhQW2Rx7pN02_6bzA@mail.gmail.com>
From: Alija Rahmanovic <rmc.aly17@gmail.com>
Date: Tue, 7 Jul 2026 06:29:46 +0200
Message-ID: 
 <CA+SKw6FYh+JLDiuL8pHZn6HoNo6LnqdONqqseCosxJj5PnUbHA@mail.gmail.com>
Subject: Re: Any known bugs with respect to data corruption in pg12/pg 14
To: Alicja Kucharczyk <zaledwie10minut@gmail.com>
Cc: Ramakrishna Reddy Nandyala <rkreddy.n@gmail.com>,
 Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000000f5360655fdd85a"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BSKw6FYh%2BJLDiuL8pHZn6HoNo6LnqdONqqseCosxJj5PnUbHA%40mail.gmail.com>
Precedence: bulk

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

=F0=9F=91=8D

V sre., 3. jun. 2026 14:33 je oseba Alicja Kucharczyk <
zaledwie10minut@gmail.com> napisala:

> Hi, for known PostgreSQL corruption-related fixes you can check this
> filtered list:
> https://why-upgrade.depesz.com/show?from=3D12&to=3D18.4&keywords=3Dcorrup=
tion.
>
> To identify problematic objects/blocks, I would first try a classic
> read-through test with pg_dump dbname > /dev/null 2> errors.log, but be
> careful because this can be heavy on a busy production system.
>

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

<div dir=3D"auto">=F0=9F=91=8D=C2=A0</div><br><div class=3D"gmail_quote gma=
il_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">V sre., 3. jun. 2=
026 14:33 je oseba Alicja Kucharczyk &lt;<a href=3D"mailto:zaledwie10minut@=
gmail.com">zaledwie10minut@gmail.com</a>&gt; napisala:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr">Hi, for known PostgreSQL corruption-re=
lated fixes you can check this filtered list: <a href=3D"https://why-upgrad=
e.depesz.com/show?from=3D12&amp;to=3D18.4&amp;keywords=3Dcorruption" target=
=3D"_blank" rel=3D"noreferrer">https://why-upgrade.depesz.com/show?from=3D1=
2&amp;to=3D18.4&amp;keywords=3Dcorruption</a>.<br><br>To identify problemat=
ic objects/blocks, I would first try a classic read-through test with pg_du=
mp dbname &gt; /dev/null 2&gt; errors.log, but be careful because this can =
be heavy on a busy production system.</div>
</blockquote></div>

--00000000000000f5360655fdd85a--