X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E0ABE9FB1F7 for ; Tue, 2 May 2006 17:17:51 -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 29712-07 for ; Tue, 2 May 2006 17:17:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id CCF379FB1D5 for ; Tue, 2 May 2006 17:17:43 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id A0B2D56435; Tue, 2 May 2006 15:17:42 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Tue, 2 May 2006 15:17:41 -0500 Date: Tue, 2 May 2006 15:17:41 -0500 From: "Jim C. Nasby" To: Bill Moran Cc: Bealach-na Bo , ahodgson@simkin.ca, pgsql-performance@postgresql.org Subject: Re: Why so slow? Message-ID: <20060502201740.GB97354@pervasive.com> References: <200604281043.16083@hal.medialogik.com> <20060430100346.20f010a9.wmoran@collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060430100346.20f010a9.wmoran@collaborativefusion.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060502:wmoran@collaborativefusion.com::fHplmBGv3nLCT83X:0000000 0000000000000000000000003Haj X-Hashcash: 1:20:060502:bealach_na_bo@hotmail.com::5kCdV0Hqvz4CakAw:000000000000 000000000000000000000000CrW2 X-Hashcash: 1:20:060502:ahodgson@simkin.ca::ADn/hN6LIxYChf6q:0000000000000000000 0000000000000000000000000+AS X-Hashcash: 1:20:060502:pgsql-performance@postgresql.org::SZwFl18GuDjVZ8Uw:00000 0000000000000000000000000uSD X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/42 X-Sequence-Number: 18829 On Sun, Apr 30, 2006 at 10:03:46AM -0400, Bill Moran wrote: > At this point, it seems like you need to do 2 things: > 1) Schedule lazy vacuum to run, or configure autovacuum. > 2) Schedule some downtime to run "vacuum full" to recover some disk space. > > #2 only needs done once to get you back on track, assuming that #1 is > done properly. You'll also want to reindex since vacuum full won't clean the indexes up. You might also want to read http://www.pervasivepostgres.com/instantkb13/article.aspx?id=10087 and http://www.pervasivepostgres.com/instantkb13/article.aspx?id=10116. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461