Dimitri Fontaine <dfontaine@hi-media.com> writes:
> Thanks to Andrew Gierth (irc:RhodiumToad) and after some analysis and we've
> been able to understand what happened: MaxFSMPages is not the maximum number
> of elements (tables and indexes) contained into the FSM memory, and the
> contrib believes it is.
Hmm. Actually the freespace.c code rounds that number up to the next
multiple of CHUNKPAGES:
/* Allocate page-storage arena */
nchunks = (MaxFSMPages - 1) / CHUNKPAGES + 1;
So your 2x patch is way overkill, but we do have an issue here.
regards, tom lane