Fix rare dsa_allocate() failures due to freepage.c corruption.
authorThomas Munro <tmunro@postgresql.org>
Wed, 13 Feb 2019 00:14:10 +0000 (13:14 +1300)
committerThomas Munro <tmunro@postgresql.org>
Wed, 13 Feb 2019 00:24:11 +0000 (13:24 +1300)
commit7215efdc005e694ec93678a6203dbfc714d12809
tree26c60dce90a8155452008057a2a0273bd77e01ba
parent75c46149fc2215b046aa56caaf59f8125f0e6062
Fix rare dsa_allocate() failures due to freepage.c corruption.

In a corner case, a btree page was allocated during a clean-up operation
that could cause the tracking of the largest contiguous span of free
space to get out of whack.  That was supposed to be prevented by the use
of the "soft" flag to avoid allocating internal pages during incidental
clean-up work, but the flag was ignored in the case where the FPM was
promoted from singleton format to btree format.  Repair.

Remove an obsolete comment in passing.

Back-patch to 10, where freepage.c arrived (as support for dsa.c).

Author: Robert Haas
Diagnosed-by: Thomas Munro and Robert Haas
Reported-by: Justin Pryzby, Rick Otten, Sand Stone, Arne Roland and others
Discussion: https://postgr.es/m/CAMAYy4%2Bw3NTBM5JLWFi8twhWK4%3Dk_5L4nV5%2BbYDSPu8r4b97Zg%40mail.gmail.com
src/backend/utils/mmgr/freepage.c