On Wed, May 27, 2020 at 12:16 PM Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > I do have evidence of postgres crashes because of a problem that could > be explained by this bug, so I +1 backpatching this to all supported > branches. > > (The problem I saw is a hash-join spilling data to temp tablespace, > which fills up but somehow goes undetected, then when reading the data > back it causes heap_fill_tuple to crash.)
FWIW, that seems like a plenty good enough reason for back-patching to me. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
