Vacuum suggesting doubling of max_fsm_pages
Hi folks I'm hoping somebody can demystify something for me.
I've got a test database that is going live.
During development I have not vacuum'd much, so to get started I did
"Vacuum verbose analyze".
At the end of the process it told me that vacuum needed max_fsm_pages to
be set at about 212000 (appx) to track all free pages.
I then ran it again (w/o yet changing max_fsm_pages) and it came back
asking for a number in the range of 490000.
So I set the value to 500000, restarted the server, and ran vacuum
again. This time it suggested a value of 980000.
It appears to me the requests are doubling in size, so before increasing
it again I thought I would ask here.
On Apr 27, 2006, at 11:06 AM, Kenneth Downs wrote:
I've got a test database that is going live.
During development I have not vacuum'd much, so to get started I
did "Vacuum verbose analyze".
you probably really do have a lot of spare space in the files. i'd
recommend vacuum full if you can, to compact it all since you haven't
done a vacuum regularly.
then after a while of production, see what vacuum recommends for fsm
settings.