Re: First draft of back-branch release notes is done - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: First draft of back-branch release notes is done
Date
Msg-id 20230205121047.hfjbdc7s36aiesbm@alvherre.pgsql
Whole thread Raw
In response to First draft of back-branch release notes is done  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: First draft of back-branch release notes is done
List pgsql-hackers
On 2023-Feb-03, Tom Lane wrote:

> ... at
> 
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f282b026787da69d88a35404cf62f1cc21cfbb7c
> 
> 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)



pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: pg_stat_statements and "IN" conditions
Next
From: Andres Freund
Date:
Subject: Re: undersized unions