From: Joshua D. Drake <jd@commandprompt.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Sabin Coanda <sabin.coanda@deuromedia.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: VACUUM vs auto-vacuum daemon
Date: Wed, 13 Jun 2007 08:08:56 -0700
Message-ID: <46700888.3080506@commandprompt.com> (raw)
In-Reply-To: <20070613104610.d9d06914.wmoran@collaborativefusion.com>
References: <f4mfin$1vjf$1@news.hub.org>
<20070612122555.2b0f4fa0.wmoran@collaborativefusion.com>
<f4micm$1cq6$1@news.hub.org>
<20070613104610.d9d06914.wmoran@collaborativefusion.com>
Bill Moran wrote:
> In response to "Sabin Coanda" <sabin.coanda@deuromedia.ro>:
>
>> Hi Bill,
>>
>> ...
>>> However, you can get some measure of tracking my running VACUUM VERBOSE
>>> on a regular basis to see how well autovacuum is keeping up. There's
>>> no problem with running manual vacuum and autovacuum together, and you'll
>>> be able to gather _some_ information about how well autovacuum is
>>> keeping up.
>> Well, I think it is useful just if I am able to synchronize the autovacuum
>> to run always after I run vacuum verbose. But I don't know how to do that.
>> Do you ?
>
> No, I don't. Why would you want to do that?
>
> Personally, I'd be more interested in whether autovacuum, running whenever
> it wants without me knowing, is keeping the table bloat under control.
analyze verbose.
>
> If this were a concern for me (which it was during initial testing of
> our DB) I would run vacuum verbose once a day to watch sizes and what
> not. After a while, I'd switch to once a week, then probably settle on
> once a month to ensure nothing ever gets out of hand. Put it in a cron
> job and have the output mailed.
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
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-performance@postgresql.org
Cc: jd@commandprompt.com, wmoran@collaborativefusion.com, sabin.coanda@deuromedia.ro
Subject: Re: VACUUM vs auto-vacuum daemon
In-Reply-To: <46700888.3080506@commandprompt.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