Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CCDF89FB542 for ; Wed, 13 Jun 2007 12:08:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 94682-04 for ; Wed, 13 Jun 2007 12:08:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id D437F9FB47F for ; Wed, 13 Jun 2007 12:08:07 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5DF7ra5010677; Wed, 13 Jun 2007 08:07:53 -0700 Message-ID: <46700888.3080506@commandprompt.com> Date: Wed, 13 Jun 2007 08:08:56 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Bill Moran CC: Sabin Coanda , pgsql-performance@postgresql.org Subject: Re: VACUUM vs auto-vacuum daemon References: <20070612122555.2b0f4fa0.wmoran@collaborativefusion.com> <20070613104610.d9d06914.wmoran@collaborativefusion.com> In-Reply-To: <20070613104610.d9d06914.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 13 Jun 2007 08:07:56 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/237 X-Sequence-Number: 25270 Bill Moran wrote: > In response to "Sabin Coanda" : > >> 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/