public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alicja Kucharczyk <[email protected]>
To: Ramakrishna Reddy Nandyala <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Any known bugs with respect to data corruption in pg12/pg 14
Date: Wed, 3 Jun 2026 14:32:41 +0200
Message-ID: <CAM=sWa4JmWhMzpJRyVdFw5h+gjE9Q3RoOrhQW2Rx7pN02_6bzA@mail.gmail.com> (raw)
In-Reply-To: <CA++_dZP4ygDekyvxmYbM8=egGshB4CRAd1mBHrdusO3CXzYwuw@mail.gmail.com>
References: <CANzqJaCNaqhQ9duPP+eKU2OR1wjGYW-FBQ2FZXqnBRb6XAnKQA@mail.gmail.com>
<[email protected]>
<CANzqJaCJGS9S=ibJ_rOmP=acA7n0XCA5R4FbMH+AH3WURhey8Q@mail.gmail.com>
<[email protected]>
<CANzqJaAb149k3pYmbnZ8-Mcc7Ec_DwJMkKiZK=tPA34Rsq_kDw@mail.gmail.com>
<CA++_dZP4ygDekyvxmYbM8=egGshB4CRAd1mBHrdusO3CXzYwuw@mail.gmail.com>
Hi, for known PostgreSQL corruption-related fixes you can check this
filtered list:
https://why-upgrade.depesz.com/show?from=12&to=18.4&keywords=corruption.
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.
view thread (7+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Any known bugs with respect to data corruption in pg12/pg 14
In-Reply-To: <CAM=sWa4JmWhMzpJRyVdFw5h+gjE9Q3RoOrhQW2Rx7pN02_6bzA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox