From: | Stef <svb(at)ucs(dot)co(dot)za> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | Markus Benne <markus(at)m-bass(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL vs CLUSTER |
Date: | 2005-09-23 17:18:03 |
Message-ID: | 20050923191803.14fff2a1@svb.ucs.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Bruno Wolff III mentioned :
=> > => If you have a proper FSM setting you shouldn't need to do vacuum fulls
=> > => (unless you have an older version of postgres where index bloat might
=> > => be an issue).
Thanks Alvaro and Bruno
I just want to clarify something that I also couldn't
find a clear cut answer for before.
What is a proper fsm setting?
Someone told me to set max_fsm_relations to the number of
relations in pg_class plus a few more to allow for new relations.
And max_fsm_pages to the number of rows in the biggest table I
want to vacuum, plus a few 1000's for extra room?
Where does this free space map sit? On the disk somewhere,
or in memory, or both.
I once set the max_fsm_pages very high by mistake, and postgres
then started up and used a _lot_ of shared memory, and I had to
increase shmmax. Is there abything to watch out for when bumping this
setting up a lot?
Kind Regards
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Lewis | 2005-09-23 17:43:02 | Re: [PERFORM] Releasing memory during External sorting? |
Previous Message | Tom Lane | 2005-09-23 17:17:24 | Re: [PERFORM] Releasing memory during External sorting? |