From: Matthew T. O'Connor <matthew@zeut.net>
To: Enzo Daddario <enzo@pienetworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum
Date: Thu, 26 Jan 2006 09:41:08 -0500 (EST)
Message-ID: <5001.71.40.140.99.1138286468.squirrel@mail.tocr.com> (raw)
In-Reply-To: <1137992841.28304.48.camel@localhost.localdomain>
References: <1137992841.28304.48.camel@localhost.localdomain>
Legit concern. However one of the things that autovacuum is supposed to
do is not vacuum tables that don't need it. This can result in an overal
reduction in vacuum overhead. In addition, if you see that autovacuum is
firing off vacuum commands during the day and they are impacting your
response time, then you can play with the vacuum cost delay settings that
are design to throttle down the IO impact vacuum commands can have. In
addition if you use 8.1, you can set per table thresholds, per table
vacuum cost delay settings, and autovacuum will respect the work done by
non-autovacuum vacuum commands. Meaning that if you manually vacuum
tables at night during a maintenance window, autovacuum will take that
into account. Contrib autovacuum couldn't do this.
Hope that helps. Real world feed-back is always welcome.
Matt
> I am concerned with the impact autovacuum of table(s) would have on
> regular DB activity.
>
> With our current DB's the majority of tables have either a low number of
> updates or a large number of inserts (which I believe should not be a
> problem), however, a small number of tables have an extremely high
> number of updates (up to 150 000)
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: matthew@zeut.net, enzo@pienetworks.com
Subject: Re: autovacuum
In-Reply-To: <5001.71.40.140.99.1138286468.squirrel@mail.tocr.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