Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id A03B8475AF8 for ; Fri, 1 Nov 2002 22:48:12 -0500 (EST) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id D5B31475A7F for ; Fri, 1 Nov 2002 22:48:10 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id gA23m0w10244; Fri, 1 Nov 2002 22:48:00 -0500 (EST) From: Bruce Momjian Message-Id: <200211020348.gA23m0w10244@candle.pha.pa.us> Subject: Re: Different size in the DATA directory In-Reply-To: <3DC2A578.6040605@perdue.net> To: Tim Perdue Date: Fri, 1 Nov 2002 22:48:00 -0500 (EST) Cc: =?ISO-8859-1?Q?Maur=EDcio_Sessue_Otta?= , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/29 X-Sequence-Number: 10171 Tim Perdue wrote: > I had this same problem with 7.1.x, even doing full vacuums on > SourceForge.net last year. > > I assumed after a while that there was some hidden bug where file bloat > occurred, despite the vacuum. After 3 months or so, you'd have to > dump/restore the entire db and you'd be golden for a while again. After > the dump/restore process things seemed much snappier too, and vacuum ran > almost instantly. > > I haven't verified if this problem still occurs in 7.2.x, using vacuum full. Tim, I guess your problem is dead index pages that can't be reclaimed, and it isn't fixed in 7.3. Only REINDEX fixes it, and we have a /contrib/reindexdb script in 7.3. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073