From: Tommy Gildseth <tommy.gildseth@usit.uio.no>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: Devendra Singh Rawat <Devendra_Rawat@infosys.com>
Subject: Re: Disk Space issue
Date: Wed, 11 Jun 2008 10:57:38 +0200
Message-ID: <484F9382.2090508@usit.uio.no> (raw)
In-Reply-To: <4242E42288B6E842A52B88D4B3A3E620E069CA69@AUSMELMBX01.ad.infosys.com>
References: <84D57263D486374587DA0820E60A2CC601E72AFF@srit_mail.renaissance-it.com>
<4242E42288B6E842A52B88D4B3A3E620E069CA69@AUSMELMBX01.ad.infosys.com>
Devendra Singh Rawat wrote:
> Hi All,
>
> I recreated my database this morning with a dump size of 3GB, which after database creation occupied 3.5GB on disk.
> And in less than 8 hours it has bloated to additional 3.7GB (the disk size now is 7.2GB).
>
> There are quite a few DML operations which are happening on my DB.
This is a typical case where you can experience a good deal of index
bloat. I would recommend installing the dbsize contrib module, and
monitor the size of the relations (tables and indexes) in your database,
to see which relations in particular is growing rapidly in size.
Once you've identified the culprit, you could use reindex or cluster to
reclaim the dead space.
Note that reindex and cluster require fairly extensive locks, so not so
good to use on a busy database during working hours.
--
Tommy Gildseth
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-admin@postgresql.org
Cc: tommy.gildseth@usit.uio.no, Devendra_Rawat@infosys.com
Subject: Re: Disk Space issue
In-Reply-To: <484F9382.2090508@usit.uio.no>
* 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