From: Scott Marlowe <scott.marlowe@gmail.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: What is VACUUM waiting for?
Date: Sun, 14 Dec 2008 11:32:16 -0700
Message-ID: <dcc563d10812141032u57652d91ra360c3526b2738c3@mail.gmail.com> (raw)
In-Reply-To: <200812141927.43106@zmi.at>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, michael.monnerie@is.it-management.at
Subject: Re: What is VACUUM waiting for?
In-Reply-To: <dcc563d10812141032u57652d91ra360c3526b2738c3@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox