>> What we do in some similar cases is put the burden on initdb to fill in
>> the correct value by modifying postgresql.conf.sample appropriately.
>> It seems like that could be done easily here too. And it'd be a
>> back-patchable fix.
>
> I haven't realized initdb can do that. I agree that would be the best
> solution.
Indeed.
Maybe something like the following, or maybe it should include "bufmgr.h",
not sure.
--
Fabien.
