Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 321DF9FA0C4 for ; Thu, 19 Apr 2007 11:53:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 58938-02 for ; Thu, 19 Apr 2007 11:53:31 -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 AD2459F9A79 for ; Thu, 19 Apr 2007 11:53:31 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-221-161.bk12-dsl.surnet.cl [201.221.221.161]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l3JErNnW026545; Thu, 19 Apr 2007 07:53:24 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id E28C132A0C; Thu, 19 Apr 2007 10:53:20 -0400 (CLT) Date: Thu, 19 Apr 2007 10:53:20 -0400 From: Alvaro Herrera To: Carol Walter Cc: Robert Treat , pgsql-admin@postgresql.org, Tom Lane Subject: Re: Auto vacuum Message-ID: <20070419145320.GD8402@alvh.no-ip.org> Mail-Followup-To: Carol Walter , Robert Treat , pgsql-admin@postgresql.org, Tom Lane References: <12357.1176841845@sss.pgh.pa.us> <200704172157.54249.robert@omniti.com> <12A54BAC-0218-40F8-9A8A-26C6268D1617@indiana.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <12A54BAC-0218-40F8-9A8A-26C6268D1617@indiana.edu> User-Agent: Mutt/1.5.13 (2006-08-11) 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]); Thu, 19 Apr 2007 07:53:24 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/180 X-Sequence-Number: 25244 Carol Walter wrote: > Robert, > > I did as you suggested and the values for autovacuum are null, > therefore I'm guessing it isn't running. Since postgres reports that > it is running, what other things might keep in from running? Too high thresholds? All tables disabled in pg_autovacuum? naptime set too high? I suggest you turn log_min_messages more verbose, to DEBUG2, and see if there are any entries in there regarding autovacuum. If it's running, you would see it. You would get a message after autovacuum_naptime seconds. How long is autovacuum_naptime anyway? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support