Thomas Munro <thomas.munro@enterprisedb.com> writes:
> This brings us to a difficult choice: we're about to cut a new
> release, and this could in theory be included. Even though the fix is
> quite convincing, it doesn't seem wise to change such complicated code
> at the last minute, and I know from an off-list chat that that is also
> Robert's view.
Yeah ... at this point we're just too close to the release deadline,
I'm afraid, even though the fix *looks* pretty safe. Not worth the risk
given that this seems to be a low-probability bug.
I observe from
https://coverage.postgresql.org/src/backend/utils/mmgr/freepage.c.gcov.html
that the edge cases in this function aren't too well exercised by
our regression tests, meaning that the buildfarm might not prove
much either way about the correctness of this patch. That is one
factor pushing me to think we shouldn't risk it. But, taking a
longer view, is that something that's practical to improve?
> So I'll wait until after the release, and we'll have
> to live with the bug for another 3 months.
Check. Please hold off committing until you see the release tags
appear, probably late Tuesday my time / Wednesday noonish yours.
regards, tom lane