From: Bill Moran <wmoran@collaborativefusion.com>
To: Sabin Coanda <sabin.coanda@deuromedia.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: VACUUM vs auto-vacuum daemon
Date: Tue, 12 Jun 2007 12:25:55 -0400
Message-ID: <20070612122555.2b0f4fa0.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <f4mfin$1vjf$1@news.hub.org>
References: <f4mfin$1vjf$1@news.hub.org>
In response to "Sabin Coanda" <sabin.coanda@deuromedia.ro>:
> Hi there,
>
> Using explicitly VACUUM command give me the opportunity to fine tune my
> VACUUM scheduling parameters, after I analyze the log generated by VACUUM
> VERBOSE.
>
> On the other hand I'd like to use the auto-vacuum mechanism because of its
> facilities. Unfortunately, after I made some initial estimations for
> autovacuum_naptime, and I set the specific data into pg_autovacuum table, I
> have not a feedback from the auto-vacuum mechanism to check that it works
> well or not. It would be nice to have some kind of log similar with the one
> generated by VACUUM VERBOSE. Is the auto-vacuum mechanism able to provide
> such a useful log ?
Ditto what Alvaro said.
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.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
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: wmoran@collaborativefusion.com, sabin.coanda@deuromedia.ro
Subject: Re: VACUUM vs auto-vacuum daemon
In-Reply-To: <20070612122555.2b0f4fa0.wmoran@collaborativefusion.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