DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=hXHz7cdvtvXklqR9lJ6XRjhvD9RVeAtissRgrwbDUw1nueMAch7i1vg/E2yBgV/Qiv
	/8OQalRBO7iTdF7bcDoN9AWlvDyuLxtfpxXGtUOxT6GH+tBlrkDkcatx8VWc1Y/qZMX1
	AeVpzzqUPDJThqJWYN07QDl0VdwdrHJGoYer4=
Message-ID: <dcc563d10812141032u57652d91ra360c3526b2738c3@mail.gmail.com>
Date: Sun, 14 Dec 2008 11:32:16 -0700
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Michael Monnerie" <michael.monnerie@is.it-management.at>
Subject: Re: What is VACUUM waiting for?
Cc: pgsql-admin@postgresql.org
In-Reply-To: <200812141927.43106@zmi.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200812122355.25481@zmi.at> <4943C70C.9070307@zeut.net>
	<200812141927.43106@zmi.at>

On Sun, Dec 14, 2008 at 11:27 AM, Michael Monnerie
<michael.monnerie@is.it-management.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.