| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ofer Israeli <oferi(at)checkpoint(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Netta Kabala <nettak(at)checkpoint(dot)com>, Olga Vingurt <olgavi(at)checkpoint(dot)com> |
| Subject: | Re: Vacuuming problems on TOAST table |
| Date: | 2012-02-08 19:44:04 |
| Message-ID: | 29376.1328730244@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Ofer Israeli <oferi(at)checkpoint(dot)com> writes:
> During our testing we see that the table size increases substantially. When looking at the autovacuum log, set with default configuration, it seems that it ran for around 60 seconds (see below and note that this was a 1-minute test, i.e. only 100 updates)!
autovacuum is intended to run fairly slowly, so as to not consume too
much resources. If you think it's too slow you can adjust the
autovacuum_cost tunables.
> When setting a higher cost for the autovacuum, tried values of 2000, it ran for even longer: ~400 seconds!
That's the wrong direction, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Traster | 2012-02-08 19:58:57 | Re: index scan forward vs backward = speed difference of 357X slower! |
| Previous Message | Ofer Israeli | 2012-02-08 19:33:59 | Vacuuming problems on TOAST table |