Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 297AC9FB38E for ; Sat, 14 Jul 2007 12:51:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 00585-02 for ; Sat, 14 Jul 2007 12:50:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.de [194.25.134.81]) by postgresql.org (Postfix) with ESMTP id 5978A9FA4DB for ; Sat, 14 Jul 2007 12:51:04 -0300 (ADT) Received: from fwd30.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1I9jtX-00028m-07; Sat, 14 Jul 2007 17:50:55 +0200 Received: from [192.168.1.2] (XRwW-MZS8eTkDDUwH3SY5JZZ0y3GFiBJLlRofyR6YXFNpPkuWhbrkz@[87.177.103.40]) by fwd30.aul.t-online.de with esmtp id 1I9jtS-0YVub20; Sat, 14 Jul 2007 17:50:50 +0200 Message-ID: <4698F0CF.7000602@p-dw.com> Date: Sat, 14 Jul 2007 17:50:39 +0200 From: Patric de Waha User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Vacuum full considered useful ;) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ID: XRwW-MZS8eTkDDUwH3SY5JZZ0y3GFiBJLlRofyR6YXFNpPkuWhbrkz@t-dialin.net X-TOI-MSGID: 39f0151c-91ee-41b2-af42-927491a0fd83 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.591 tagged_above=0 required=5 tests=AWL=-0.807, BAYES_50=0.001, FH_HAS_XID=2.397 X-Spam-Level: * X-Archive-Number: 200707/171 X-Sequence-Number: 25855 Hi, Something I'd like to share. I switched to postgres about 4 months ago. The perfomance after a while got worse. I posted a message here, where the result was that my IO was the problem. I run vacuum every night. I never used vacuum full because it is not explicitly recommended and I read somewhere in the archives a mail that the consistency of the db suffered after a vacuum full run. Yesterday I switched from 8.1 to 8.2. So I needed to dump the dbase and reimport it. The dbase after 4 months of running without "vacuum full" reached 60 gigabyte of diskspace. Now after a fresh import it only has 5 gigabyte! No wonder, I got IO problems with such a fragmentation. For people not very familiar with postgres especially those coming from mysql, i'd recommend paying attention to this. regards, patric de waha