Received: from maia.hub.org (maia-4.hub.org [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B6A82633C2C for ; Wed, 5 May 2010 09:08:46 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 09585-02-5 for ; Wed, 5 May 2010 12:08:36 +0000 (UTC) X-Greylist: delayed 00:25:56.125456 by SQLgrey-1.7.6 Received: from miranda.sommitrealweird.co.uk (miranda.sommitrealweird.co.uk [195.10.223.140]) by mail.postgresql.org (Postfix) with ESMTP id AA7FB634385 for ; Wed, 5 May 2010 09:08:09 -0300 (ADT) Received: from brettp by miranda.sommitrealweird.co.uk with local (Exim 4.69) (envelope-from ) id 1O9czS-0006Eu-Pm for pgsql-admin@postgresql.org; Wed, 05 May 2010 12:42:10 +0100 Date: Wed, 5 May 2010 12:42:10 +0100 From: Brett Parker To: pgsql-admin@postgresql.org Subject: Re: Table space grow big - PostgreSQL Message-ID: <20100505114210.GD16616@miranda> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201005/54 X-Sequence-Number: 34527 On 05 May 13:36, Khangelani Gama wrote: > Hi all > > > Please assist on this scenario, I am a junior DBA, perhaps the > question I have is too simple please bear with me. > > I have a server with one PostgreSQL database and the data reside in > /usr/local/pgsql/data/ running on Redhat 9 O/S. > The main question I have is: What makes the > /usr/local/pgsql/data/base/95186722/ grow so big while the actual > data with its schema is only 2.8G and that is there a way to reduce > the table space sizes or anything related to that? OK - what version of postgres would be a good starting question... But, at a guess, I'd say you have a fair amount of table churn, and that you're probably due running a VACUUM FULL over the database that is using the most space, it may fail, but if it does it should tell you what bit of config you'll need to change to make it work. The other possible usage of lots of space is indexes on the database tables, these are not included in the dump, and so the size of the dump doesn't accurately reflect the size of the on disc data. Hope that gives you somewhere to start from. Thanks, -- Brett Parker