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

From Tom Lane
Subject Re: First draft of back-branch release notes is done
Date
Msg-id 2522985.1675627763@sss.pgh.pa.us
Whole thread Raw
In response to Re: First draft of back-branch release notes is done  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>> 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?

Maybe less scary if we make it clear we're talking about a temporary file?

     <para>
      Fix edge-case corruption of temporary data within shared tuplestores
      (Dmitry Astapov)
     </para>

     <para>
      If the final chunk of a large tuple being written out to a temporary
      file 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.
     </para>

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: First draft of back-branch release notes is done
Next
From: Thomas Munro
Date:
Subject: Re: First draft of back-branch release notes is done