Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 36DB29FA31B for ; Thu, 4 Jan 2007 06:34:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 40908-03 for ; Thu, 4 Jan 2007 06:34:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 1CC959FA131 for ; Thu, 4 Jan 2007 06:34:29 -0400 (AST) thread-index: Accv6+1ixe5D0vHGSBGNiK73GXFDww== Received: from [192.168.0.22] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 4 Jan 2007 05:34:33 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 Content-Class: urn:content-classes:message Importance: normal Subject: Re: Autovacuum not running in 8.2.0 From: "Simon Riggs" To: "Ming" Cc: In-Reply-To: <4fc81d760701032030x383f7fd2m86af3449db27e189@mail.gmail.com> References: <4fc81d760701032030x383f7fd2m86af3449db27e189@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 04 Jan 2007 10:33:41 +0000 Message-ID: <1167906821.3903.651.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Jan 2007 10:34:34.0484 (UTC) FILETIME=[ED167340:01C72FEB] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/20 X-Sequence-Number: 24176 On Thu, 2007-01-04 at 11:30 +0700, Ming wrote: > Hi, I recently upgraded from 8.1.4 to 8.2.0, everything was fine > except that I suspect that the autovacuum was not running. In > pgAdmin's server properties, the "Autovacuum" property shows > "runnning", but I couldn't find any log entry for the autovacuum > process. I've set the new postgresql.conf to match the old one (from > the 8.1.4 install), especially the autovacuum entries, but still I > couldn't find any log entry for the process (The logging works fine, I > tried to supply a wrong login password, and the login failure was > successfully logged). Has anyone experienced similar issue? Yes, its not very easy to determine if it is working, and if it is, what it has done. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com