Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0F8EA9FA42F for ; Thu, 4 Jan 2007 00:30:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 36599-10 for ; Thu, 4 Jan 2007 00:30:35 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.239]) by postgresql.org (Postfix) with ESMTP id 6EFBA9F931E for ; Thu, 4 Jan 2007 00:30:35 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id i11so2885561nzh for ; Wed, 03 Jan 2007 20:30:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=pjezrUbk2i3+6PFl6X/ytAvW7plWLfBQnFsVyb6il8vhUzrhHXJsAwCz6i0fT0Yal45fa7wSkj75oJcQgarGj2OXkWcsMhHm9JLXhNZThYdwT/QZPzxDvGU7hqWhW0AMInIFOpsMUP4masDp4iHITS5E+j4oP7Bj8kshYs5ycyY= Received: by 10.65.122.20 with SMTP id z20mr13477291qbm.1167885034705; Wed, 03 Jan 2007 20:30:34 -0800 (PST) Received: by 10.64.10.10 with HTTP; Wed, 3 Jan 2007 20:30:34 -0800 (PST) Message-ID: <4fc81d760701032030x383f7fd2m86af3449db27e189@mail.gmail.com> Date: Thu, 4 Jan 2007 11:30:34 +0700 From: Ming To: pgsql-admin@postgresql.org Subject: Autovacuum not running in 8.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/14 X-Sequence-Number: 24170 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? Regards, Ming