Jim Jones <jim.jones@uni-muenster.de> writes:
> Out of curiosity, why aren't we applying this to v18?
Our risk-aversion level rises steadily over the course of a release
cycle, and is pretty high post beta1. While I think the problems
we're trying to fix here are real, they are very low-probability
(I don't recall hearing any field reports traceable to this).
And you have to remember there is also some risk of introducing
new bugs. On balance it's not a change I would back-patch, and
at this point v18 is pretty close to being a stable branch so
it's not getting fixes we wouldn't back-patch, unless that's
because they are in new-in-18 code.
tl;dr: I agree with Michael's choice to hold it for v19.
It's a judgment call of course, but I think it's the right one.
regards, tom lane