Re: Vacuum wait time problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Vacuum wait time problem
Date: 2009-02-14 02:02:43
Message-ID: 23106.1234576963@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Fri, Feb 13, 2009 at 5:02 PM, Michael Monnerie
> <michael(dot)monnerie(at)is(dot)it-management(dot)at> wrote:
>> vacuum_cost_delay = 0
>> That was the trick for me. It was set to 250(ms), where it took 5 hours
>> for a vacuum to run. Now it takes 5-15 minutes.

> Wow!!! 250 ms is HUGE in the scheme of vacuum cost delay. even 10ms
> is usually plenty to slow down vacuum enough to keep it out of your
> way and double to quadruple your vacuum times.

I wonder whether we ought to tighten the allowed range of
vacuum_cost_delay. The upper limit is 1000ms at the moment;
but that's clearly much higher than is useful, and it seems
to encourage people to pick silly values ...

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2009-02-14 02:24:32 Re: Vacuum wait time problem
Previous Message Scott Marlowe 2009-02-14 01:08:12 Re: Vacuum wait time problem