From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Costin Grigoras <costing(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: why is autovacuum still ongoing even if set to off ? |
Date: | 2009-07-31 06:41:38 |
Message-ID: | dcc563d10907302341w731c6fe9uc430c56cad3f2793@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 31, 2009 at 12:24 AM, Costin Grigoras<costing(at)gmail(dot)com> wrote:
>
>> Anytime autovacuum is instrusive look at incrementing the nap time to
>> 10 to 20 ms. If that doesn't help then you're already running on the
>> ragged edge of IO throughput and might need to look into a faster RAID
>> array or something.
>>
>
> => show autovacuum_naptime;
> autovacuum_naptime
> --------------------
> 100h
Dangit, I meant cost delay... urg. That's a really long naptime, but
since you vacuum anyway it shouldn't matter.
So, after disabling autovacuum in postgresql.conf, you reloaded /
restart postgresql, right?
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-07-31 06:45:58 | Re: why is autovacuum still ongoing even if set to off ? |
Previous Message | Costin Grigoras | 2009-07-31 06:24:18 | Re: why is autovacuum still ongoing even if set to off ? |