From: Adrian Moisey <adrian@careerjunction.co.za>
To: pgsql-performance@postgresql.org
Subject: Re: db size
Date: Tue, 15 Apr 2008 09:33:06 +0200
Message-ID: <48045A32.3010607@careerjunction.co.za> (raw)
In-Reply-To: <op.t9lh5em8cigqcu@apollo13.peufeu.com>
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>
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
--
Adrian Moisey
Systems Administrator | CareerJunction | Your Future Starts Here.
Web: www.careerjunction.co.za | Email: adrian@careerjunction.co.za
Phone: +27 21 686 6820 | Mobile: +27 82 858 7830 | Fax: +27 21 686 6842
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: adrian@careerjunction.co.za
Subject: Re: db size
In-Reply-To: <48045A32.3010607@careerjunction.co.za>
* 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