public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: First draft of back-branch release notes is done
Date: Sun, 5 Feb 2023 13:10:47 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2023-Feb-03, Tom Lane wrote:
> ... at
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f282b026787da69d88a35404cf62f1cc2...
>
> As usual, please send corrections/comments by Sunday.
Fix edge-case data corruption in shared tuplestores (Dmitry Astapov)
If the final chunk of a large tuple being written out to disk was
exactly 32760 bytes, it would be corrupted due to a fencepost bug.
This is a hazard for parallelized plans that require a tuplestore,
such as parallel hash join. The query would typically fail later
with corrupted-data symptoms.
I think this sounds really scary, because people are going to think that
their stored data can get corrupted -- they don't necessarily know what
a "shared tuplestore" is. Maybe "Avoid query failures in parallel hash
joins" as headline?
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"The Gord often wonders why people threaten never to come back after they've
been told never to return" (www.actsofgord.com)
view thread (5+ messages) latest in thread
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: First draft of back-branch release notes is done
In-Reply-To: <[email protected]>
* 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