From: Alvaro Herrera <alvherre@commandprompt.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:08:02 -0400
Message-ID: <20070612160802.GC15517@alvh.no-ip.org> (raw)
In-Reply-To: <f4mfin$1vjf$1@news.hub.org>
References: <f4mfin$1vjf$1@news.hub.org>
Sabin Coanda wrote:
> 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 ?
No, sorry, autovacuum is not currently very good regarding reporting its
activities. It's a lot better in 8.3 but even there it doesn't report
the full VACUUM VERBOSE log. It looks like this:
LOG: automatic vacuum of table "alvherre.public.foo": index scans: 0
pages: 45 removed, 0 remain
tuples: 10000 removed, 0 remain
system usage: CPU 0.00s/0.00u sec elapsed 0.01 sec
LOG: automatic analyze of table "alvherre.public.foo" system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
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: alvherre@commandprompt.com, sabin.coanda@deuromedia.ro
Subject: Re: VACUUM vs auto-vacuum daemon
In-Reply-To: <20070612160802.GC15517@alvh.no-ip.org>
* 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