Date: Tue, 15 Apr 2008 07:12:22 -0400
From: Bill Moran <wmoran@collaborativefusion.com>
To: Adrian Moisey <adrian@careerjunction.co.za>
Cc: pgsql-performance@postgresql.org
Subject: Re: db size
Message-Id: <20080415071222.36b2e8eb.wmoran@collaborativefusion.com>
In-Reply-To: <48045A32.3010607@careerjunction.co.za>
References: <4802F9E4.3000704@careerjunction.co.za>
	<op.t9lf4tvrcigqcu@apollo13.peufeu.com>
	<48032237.4040604@careerjunction.co.za>
	<op.t9lgusticigqcu@apollo13.peufeu.com>
	<4803276C.2090901@careerjunction.co.za>
	<op.t9lh5em8cigqcu@apollo13.peufeu.com>
	<48045A32.3010607@careerjunction.co.za>
Organization: Collaborative Fusion Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Adrian Moisey <adrian@careerjunction.co.za> wrote:
>
> Hi
> 
> >>>     Now, is the bloat in the tables (which tables ?) or in the 
> >>> indexes (which indexes ?), or in the toast tables perhaps, or in the 
> >>> system catalogs or all of the above ? Or perhaps there is a 
> >>> long-forgotten process that got zombified while holding a huge temp 
> >>> table ? (not very likely, but who knows).
> >>>     Use pg_relation_size() and its friends to get an idea of the size 
> >>> of stuff.
> 
> Can anybody give me some advice on the above?  I'm not sure where to 
> start looking or how to start looking

Running VACUUM VERBOSE will give you a detailed view of space usage of
each individual table.

-- 
Bill Moran
Collaborative Fusion Inc.

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023