Re: First draft of back-branch release notes is done
От | Tom Lane |
---|---|
Тема | Re: First draft of back-branch release notes is done |
Дата | |
Msg-id | 2521820.1675627059@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: First draft of back-branch release notes is done (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: First draft of back-branch release notes is done
Re: First draft of back-branch release notes is done |
Список | pgsql-hackers |
Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > On 2023-Feb-03, Tom Lane wrote: >> Fix edge-case data corruption in shared tuplestores (Dmitry Astapov) > 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? Hmmm ... are we sure it *can't* lead to corruption of stored data, if this happens during an INSERT or UPDATE plan? I'll grant that such a case seems pretty unlikely though, as the bogus data retrieved from the tuplestore would have to not cause a failure within the query before it can get written out. Also, aren't shared tuplestores used in more places than just parallel hash join? I mentioned that as an example, not an exhaustive list of trouble spots. regards, tom lane
В списке pgsql-hackers по дате отправления: