X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 292C2D1D2A4 for ; Thu, 8 Apr 2004 10:33:28 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 31296-05 for ; Thu, 8 Apr 2004 10:33:28 -0300 (ADT) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by svr1.postgresql.org (Postfix) with ESMTP id 8F1D2D1D098 for ; Thu, 8 Apr 2004 10:33:25 -0300 (ADT) Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i38DXOJW003268 for ; Thu, 8 Apr 2004 15:33:24 +0200 (CEST) Received: from obiou.imag.fr ([129.88.43.2] ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BBZem-0003yQ-00 for ; Thu, 08 Apr 2004 15:33:24 +0200 Date: Thu, 8 Apr 2004 15:33:24 +0200 (MEST) From: Nicolas Kowalski X-X-Sender: kowalski@obiou.imag.fr To: pgsql-admin@postgresql.org Subject: Re: Database storage bloat In-Reply-To: <272e4be7.0404080115.39f1cb36@posting.google.com> Message-ID: References: <272e4be7.0404080115.39f1cb36@posting.google.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/145 X-Sequence-Number: 13118 On Thu, 8 Apr 2004, Tony Reina wrote: > Has anyone run across similar storage concerns? I'd be interested in > knowing if I just have really poorly designed tables, or if something > else is going on here. I figure a bloat of 3-4X would be permissible > (and possibly expected). But this bloat just seems too much. Yes, however my example is not very accurate because we are still running an old version (7.2.1, Debian stable). In our case, dump file created from pg_dumpall is around 4 MB, but the data directory is around 180MB. Regards. -- Nicolas