Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4828D9FBD86 for ; Wed, 21 Feb 2007 16:38:42 -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 64529-01 for ; Wed, 21 Feb 2007 16:38:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by postgresql.org (Postfix) with ESMTP id 191619FBD6A for ; Wed, 21 Feb 2007 16:38:39 -0400 (AST) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 194311C7254; Wed, 21 Feb 2007 15:39:56 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 21 Feb 2007 15:39:56 -0500 X-Sasl-enc: i1PJrMQtqYWOQRos1f66e/CxMpwR/Zhut+2fYeT5z5AL 1172090393 Received: from [192.168.0.96] (ool-435121e8.dyn.optonline.net [67.81.33.232]) by mail.messagingengine.com (Postfix) with ESMTP id 93F231A4C5; Wed, 21 Feb 2007 15:39:53 -0500 (EST) Message-ID: <45DCAD50.8080104@zeut.net> Date: Wed, 21 Feb 2007 15:36:32 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: Mark Stosberg CC: pgsql-performance@postgresql.org Subject: Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better? References: <20070221185544.GX25424@alvh.no-ip.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.068 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200702/222 X-Sequence-Number: 23276 Mark Stosberg wrote: > Let me ask the question a different way: Is simply setting the two > values plus enabling autovacuuming generally enough, or is further > tweaking common place? No, most people in addition to setting those two GUC settings also lower the threshold values (there is a fair amount of discussion on this in the lists) the defaults are not aggressive enough, so you tables probably aren't getting vacuumed often enough to keep up with the load. Some work loads also require that you do cron based vacuuming of specific highly active tables. > Perhaps I'll give it another tree when we upgrade to 8.2. Autovacuum is still somewhat new, and there were some significant improvements in 8.2 so yes you should give it another try.