From: Bill Moran <wmoran@collaborativefusion.com>
To: Adrian Moisey <adrian@careerjunction.co.za>
Cc: pgsql-performance@postgresql.org
Subject: Re: db size
Date: Tue, 15 Apr 2008 07:12:22 -0400
Message-ID: <20080415071222.36b2e8eb.wmoran@collaborativefusion.com> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: wmoran@collaborativefusion.com, adrian@careerjunction.co.za
Subject: Re: db size
In-Reply-To: <20080415071222.36b2e8eb.wmoran@collaborativefusion.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox