Kind of off-topic, but I've found that putting the history table on a separate spindle (using a separate tablespace) also helps improve performance. --Richard On Apr 8, 2010, at 12:44 PM, Robert Haas wrote: > 2010/4/8 Merlin Moncure <mmoncure@xxxxxxxxx>: >> previous to 8.2, to get good performance on zabbix you need to >> aggressively vacuum the heavily updated tables yourself. > > Generally if you DON'T vacuum aggressively enough, then vacuums will > take a really long and painful amount of time, perhaps accounting for > the "hang" the OP observed. There's really no help for it but to > sweat it out once, and then do it frequently enough afterward that it > doesn't become a problem. > > ...Robert > > -- > Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
