Re: First draft of back-branch release notes is done
От | Alvaro Herrera |
---|---|
Тема | Re: First draft of back-branch release notes is done |
Дата | |
Msg-id | 20230205121047.hfjbdc7s36aiesbm@alvherre.pgsql обсуждение исходный текст |
Ответ на | First draft of back-branch release notes is done (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: First draft of back-branch release notes is done
|
Список | 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 по дате отправления: