Re: VACUUM FULL vs CLUSTER
От | Stef |
---|---|
Тема | Re: VACUUM FULL vs CLUSTER |
Дата | |
Msg-id | 20050923191803.14fff2a1@svb.ucs.co.za обсуждение исходный текст |
Ответ на | Re: VACUUM FULL vs CLUSTER (Bruno Wolff III <bruno@wolff.to>) |
Ответы |
Re: VACUUM FULL vs CLUSTER
|
Список | 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
В списке pgsql-performance по дате отправления: