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

Re: What is VACUUM waiting for?

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Michael Monnerie" <michael(dot)monnerie(at)is(dot)it-management(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: What is VACUUM waiting for?
Date: 2008-12-14 18:32:16
Message-ID: dcc563d10812141032u57652d91ra360c3526b2738c3@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Sun, Dec 14, 2008 at 11:27 AM, Michael Monnerie
<michael(dot)monnerie(at)is(dot)it-management(dot)at> wrote:
> On Samstag 13 Dezember 2008 Matthew T. O'Connor wrote:
>> Do you have any vacuum delay setting turned on?  Perhaps they are too
>> high?
>
> Oh, I didn't remember there were some for normal vacuum, just the
> auto_vaccuum.
>
> vacuum_cost_delay = 250
> vacuum_cost_page_hit = 1
> vacuum_cost_page_miss = 10
> vacuum_cost_page_dirty = 20
> vacuum_cost_limit = 1000
>
> Are those values to high/low? What should one use?
>
> I think I will disable it at this one server, setting
> vacuum_cost_delay = 0
> because it's only one DB here. Still, I'd like to understand what values
> would be reasonable on a server with many DBs, as we have some.

Yeah, any vacuum cost_delay over 20 or so is pretty high.  I set it to
10 and vacuum doesn't get in the way but still runs reasonably fast.

In response to

pgsql-admin by date

Next:From: Jaime CasanovaDate: 2008-12-15 21:31:39
Subject: Re: Urgente error in restore prod
Previous:From: Michael MonnerieDate: 2008-12-14 18:27:42
Subject: Re: What is VACUUM waiting for?

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