Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 672AC6334F0 for ; Mon, 3 May 2010 10:47:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 84118-01 for ; Mon, 3 May 2010 13:47:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 0D5DF63326A for ; Mon, 3 May 2010 10:47:44 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 447A236438F; Mon, 3 May 2010 06:47:43 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id convU0txA2XZ; Mon, 3 May 2010 06:47:41 -0700 (PDT) Received: from perhan.alvh.no-ip.org (unknown [190.95.8.51]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id CD78636438E; Mon, 3 May 2010 06:47:40 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B07B66E99F; Mon, 3 May 2010 09:47:38 -0400 (CLT) Date: Mon, 3 May 2010 09:47:38 -0400 From: Alvaro Herrera To: Benjamin Krajmalnik Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Autovacuum stopped running Message-ID: <20100503134738.GA2986@alvh.no-ip.org> References: <4BDBF3C90200002500031147@gw.wicourts.gov> <11024.1272755375@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201005/21 X-Sequence-Number: 34494 Benjamin Krajmalnik wrote: > OK. > This happened again on another server with these same settings. > I did not see any long running transaction, and the autovacuum launch > process was running. Did you check the server log for FATAL or ERROR lines? Maybe it's dying trying to vacuum some table and isn't ever able to get to the next ones. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support