On 2020-Jan-27, Robert Haas wrote: > OK, now that I've waxed eloquent on that topic, let me have a go at > your actual questions. Regarding back-patching, I don't mind > back-patching error handling patches like this, but I don't feel it's > necessary if we have no evidence that data is actually getting > corrupted as a result of the problem and the chances of it actually > happening seems remote.
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.) Thomas, if you're no longer interested in seeing this done, please let me know and I can see to it. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
