Date: Wed, 13 Jun 2007 10:46:10 -0400
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
Message-Id: <20070613104610.d9d06914.wmoran@collaborativefusion.com>
In-Reply-To: <f4micm$1cq6$1@news.hub.org>
References: <f4mfin$1vjf$1@news.hub.org>
	<20070612122555.2b0f4fa0.wmoran@collaborativefusion.com>
	<f4micm$1cq6$1@news.hub.org>
Organization: Collaborative Fusion
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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.

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.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023