Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 61AA06504C9 for ; Wed, 30 Jul 2008 14:19:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 18846-08-3 for ; Wed, 30 Jul 2008 14:19:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by postgresql.org (Postfix) with ESMTP id 05C196503FE for ; Wed, 30 Jul 2008 14:18:34 -0300 (ADT) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by ptb-relay01.plus.net with esmtp (Exim) id 1KOFJi-0001Kg-D3; Wed, 30 Jul 2008 18:18:26 +0100 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id 27432274065; Wed, 30 Jul 2008 18:18:26 +0100 (BST) Message-ID: <4890A261.8040802@archonet.com> Date: Wed, 30 Jul 2008 18:18:25 +0100 From: Richard Huxton User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Dave North CC: pgsql-performance@postgresql.org Subject: Re: Database size Vs performance degradation References: <35FABCF85D99464FB00BC5123DC2A70A051D0FB8@s228130hz1ew09.apptix-01.savvis.net> <48905E59.9040007@archonet.com> <35FABCF85D99464FB00BC5123DC2A70A051D0FEC@s228130hz1ew09.apptix-01.savvis.net> In-Reply-To: <35FABCF85D99464FB00BC5123DC2A70A051D0FEC@s228130hz1ew09.apptix-01.savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: 5fc6cc1c534dce7a7ae8479ed7ecb0c6 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/252 X-Sequence-Number: 30852 Dave North wrote: > -----Original Message----- > From: Richard Huxton [mailto:dev@archonet.com] > > Well, that's pretty much the definition of bloat. Are you sure you're > vacuuming enough? > > DN: Well, the auto-vac is kicking off pretty darn frequently...around > once every 2 minutes. However, you just made me think of the obvious - > is it actually doing anything?! The app is pretty darn write intensive > so I wonder if it's actually able to vacuum the tables? If you've got a big batch delete, it can't hurt to manually vacuum that table immediately afterwards. -- Richard Huxton Archonet Ltd