X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B6CDE9FA42B for ; Wed, 21 Jun 2006 11:08:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 94061-05 for ; Wed, 21 Jun 2006 11:08:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.ecircle.de (mail.ecircle.de [195.140.186.200]) by postgresql.org (Postfix) with ESMTP id 85ACE9FA19B for ; Wed, 21 Jun 2006 11:08:35 -0300 (ADT) Received: from einstein.muc.ecircle.de (einstein.muc.ecircle.de [192.168.1.7]) by mail.ecircle.de (READY) with ESMTP id 6F41B55C001; Wed, 21 Jun 2006 16:08:33 +0200 (CEST) Received: from [192.168.1.91] ([192.168.1.91]) by einstein.muc.ecircle.de with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jun 2006 16:08:53 +0200 Subject: Re: Help tuning autovacuum - seeing lots of relation From: Csaba Nagy To: jody brownell Cc: postgres performance list In-Reply-To: <200606211052.43227.jody.brownell@q1labs.com> References: <200606211052.43227.jody.brownell@q1labs.com> Content-Type: text/plain Message-Id: <1150898912.3309.23.camel@coppola.muc.ecircle.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 21 Jun 2006 16:08:33 +0200 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Jun 2006 14:08:53.0966 (UTC) FILETIME=[3A8EEEE0:01C6953C] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/396 X-Sequence-Number: 19753 > So, it appears my autovacuum is just NOT working... I must have screwed something up, but I cannot see what. Is it possible that you have long running transactions ? If yes, VACUUM is simply not efficient, as it won't eliminate the dead space accumulated during the long running transaction. In that case VACUUM FULL won't help you either as it also can't eliminate dead space still visible by old transactions, but from what you say I guess you really stop everything before doing VACUUM FULL so you might as well stopped the culprit transaction too... that's why the VACUUM FULL worked (if my assumption is correct). To check if this is the case, look for "idle in transaction" in your process listing (ps auxww|grep "idle in transaction"). If you got one (or more) of that, you found your problem. If not, hopefully others will help you :-) Cheers, Csaba.