From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com> |
Cc: | Guillaume Cottenceau <gc(at)mnc(dot)ch>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: scheduling autovacuum at lean hours only. |
Date: | 2009-02-11 16:33:16 |
Message-ID: | 2f4958ff0902110833t23c93263sdcec2afa3113bac7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Feb 11, 2009 at 2:57 PM, Rajesh Kumar Mallah
<mallah(dot)rajesh(at)gmail(dot)com> wrote:
>> vacuum_cost_delay = 150
>> vacuum_cost_page_hit = 1
>> vacuum_cost_page_miss = 10
>> vacuum_cost_page_dirty = 20
>> vacuum_cost_limit = 1000
>> autovacuum_vacuum_cost_delay = 300
>
> why is it not a good idea to give end users control over when they
> want to run it ?
Effectively, you have control over autovacuum via these params.
You have to remember, that autovacuum doesn't cost much, and it makes
planner know more about data.
It's not there to clean up databases, as you might imagine - it is
there to update stats, and mark pages as free.
So make sure you tweak that config fist, because I have a funny
feeling that you just think that vacuuming bogs down your machine, and
_can_ be turned off without any bad consequences, which is simply not
true.
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | Ben | 2009-02-11 16:46:54 | Re: scheduling autovacuum at lean hours only. |
Previous Message | Alvaro Herrera | 2009-02-11 16:21:57 | Re: scheduling autovacuum at lean hours only. |