On Jan 27, 2008 5:01 PM, Thomas Lozza <thomas.lozza@xxxxxxxxxxxxxxxx> wrote: > Thanks for the advice. > I used the default settings before, thought though that vacuum was a bit > aggressive, ie, using too many resources. Now its taking very long. So > will have to find reasonable settings in between I guess. > > On the other hand, if I keep the fsm_page number high enough, the system > should be fine with a low number of vacuum cycles, right. As memory is > not really scarce (16G, 32 bit PG though) an x million fsm_page entry > should be ok. Any thoughts on that? The issue you then run into is bloat, where you have a table or index that is 90% or so empty space, and performance on selects might suffer, especially on larger tables or indexes. What often works best is to let autovacuum handle most of your tables, then schedule individual tables to be vacuumed by cron, setting the nap time for vacuum at 20 or 30 milliseconds so they don't chew up all of your I/O ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
