Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 76CA49FB508 for ; Sat, 14 Jul 2007 13:34:15 -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 11435-09 for ; Sat, 14 Jul 2007 13:33:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B86039FB452 for ; Sat, 14 Jul 2007 13:34:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6EGWmeq018551; Sat, 14 Jul 2007 12:32:48 -0400 (EDT) To: Patric de Waha cc: pgsql-performance@postgresql.org Subject: Re: Vacuum full considered useful ;) In-reply-to: <4698F0CF.7000602@p-dw.com> References: <4698F0CF.7000602@p-dw.com> Comments: In-reply-to Patric de Waha message dated "Sat, 14 Jul 2007 17:50:39 +0200" Date: Sat, 14 Jul 2007 12:32:48 -0400 Message-ID: <18550.1184430768@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/173 X-Sequence-Number: 25857 Patric de Waha writes: > 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. Indeed, but routine VACUUM FULL is not the best answer. What this suggests is that you don't have the FSM size (max_fsm_pages and possibly max_fsm_relations) set high enough for your DB size. If it isn't big enough then you'll "leak" reusable space over time. Also, if you are using manual rather than autovacuum you might need to be vacuuming more often. regards, tom lane