Skip site navigation (1) Skip section navigation (2)

Re: Finetuning Autovacuum

From: "Benjamin Krajmalnik" <kraj(at)illumen(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>,"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Finetuning Autovacuum
Date: 2010-01-05 05:00:51
Message-ID: F4E6A2751A2823418A21D4A160B68988613C67@fletch.stackdump.local (view raw or flat)
Thread:
Lists: pgsql-admin
Alvaro, Scott - thanks for your replies and the direction you pointed me
into.

The underlying problem was that the cost limit was too low, so the
autovacuum process would run forever and not be able to do anything.  I
reduced the cost delay and increased the cost limit form the default of
200 to 10000, which is slightly more than the longest time I saw when
running manually.  Autovacuum now works as expected - the tables, which
have a very high rate of updates and some inserts (very few) are not
growing anymore.  The run time for the scheduled background processes
(which perform some background aggregation) have gone down slightly
(about 10%) as well.  Since autovacuum will prevent a deadlock, it is
definitely preferable to me over manually vacuuming.

Once again, thanks! 

In response to

Responses

pgsql-admin by date

Next:From: Brad NicholsonDate: 2010-01-05 13:35:55
Subject: Re: Finetuning Autovacuum
Previous:From: Benjamin KrajmalnikDate: 2010-01-05 03:45:17
Subject: Re: Finetuning Autovacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group