Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 9BB1B2E0060 for ; Wed, 11 Jun 2008 05:59:04 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88032-02-5 for ; Wed, 11 Jun 2008 05:58:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from pat.uio.no (pat.uio.no [129.240.10.15]) by developer.postgresql.org (Postfix) with ESMTP id A51BB2E00BC for ; Wed, 11 Jun 2008 05:57:40 -0300 (ADT) Received: from mail-mx5.uio.no ([129.240.10.46]) by pat.uio.no with esmtp (Exim 4.67) (envelope-from ) id 1K6M9D-0001fa-1y; Wed, 11 Jun 2008 10:57:39 +0200 Received: from inhaca.uio.no ([129.240.6.208]) by mail-mx5.uio.no with esmtp (Exim 4.69) (envelope-from ) id 1K6M9C-0005Me-QD; Wed, 11 Jun 2008 10:57:38 +0200 Message-ID: <484F9382.2090508@usit.uio.no> Date: Wed, 11 Jun 2008 10:57:38 +0200 From: Tommy Gildseth User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" CC: Devendra Singh Rawat Subject: Re: Disk Space issue References: <84D57263D486374587DA0820E60A2CC601E72AFF@srit_mail.renaissance-it.com> <4242E42288B6E842A52B88D4B3A3E620E069CA69@AUSMELMBX01.ad.infosys.com> In-Reply-To: <4242E42288B6E842A52B88D4B3A3E620E069CA69@AUSMELMBX01.ad.infosys.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 5FB847135B8D7559E915E276E30C93512729BA28 X-UiO-SPAM-Test: remote_host: 129.240.6.208 spam_score: -49 maxlevel 200 minaction 2 bait 0 mail/h: 1 total 20 max/h 2 blacklist 0 greylist 0 ratelimit 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/96 X-Sequence-Number: 29434 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