Message-ID: <3DC2A578.6040605@perdue.net>
Date: Fri, 01 Nov 2002 10:02:00 -0600
From: Tim Perdue <tim@perdue.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.2b) Gecko/20021016
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Maur=EDcio_Sessue_Otta?= <mauricio@cristorei.com.br>,
	pgsql-sql@postgresql.org
Subject: Re: Different size in the DATA directory
References: <004901c281b0$411de2a0$cba0a2c8@cristorei.com.br>
In-Reply-To: <004901c281b0$411de2a0$cba0a2c8@cristorei.com.br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Maurício Sessue Otta wrote:

> Hi, in my production server a "du -hs" in the DATA directory
> returns 21GB
> in a newly installed server, after I restored the dumps from the
> production server, the "du -hs" gives me just 8GB
>
> why is there such a diference???
>
> what should I do (besides buying bigger and bigger HDs) ???
>
> []'s Mauricio


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