Skip site navigation (1) Skip section navigation (2)

Re: Giant Postgresql Database Cluster Folder

From: robin <robin(at)edesix(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Giant Postgresql Database Cluster Folder
Date: 2012-04-10 07:19:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Given your data set is small so a dump/restore cycle is painless, you 
should also consider upgrading to the latest stable release.

I agree with Raghu that you need to vacuum your database periodically 
to keep it's footprint under control, but rather than doing the VACUUM 
commands via scheduled activity you should use the auto vacuum daemon 
unless you have specific needs.  You probably do need to do the first 
vacuum by hand with no users connected (or do a dump/restore cycle which 
is perhaps quicker with a system as bloated as yours).

Given you missed the need to vacuum I would read the whole routine 
maintenance section in case there are other activities that you should 
be performing to keep your data safe and available:

Hope this helps,


On Tue, 10 Apr 2012 11:44:08 +0530, raghu ram wrote:
> On Tue, Apr 10, 2012 at 11:21 AM, Kiruba suthan  wrote:
>> Could you help me how to clean up DB Cluster folder and reclaim disk
>> space please? And please give me some insight into how data is
>> organized in DB Cluster and what should I do to avoid this happening
>> again?

In response to

pgsql-admin by date

Next:From: Albe LaurenzDate: 2012-04-10 12:52:45
Subject: Re: utf8 database not dumping utf8 characters
Previous:From: raghu ramDate: 2012-04-10 06:19:39
Subject: Re: Why would queries fail with 'could not stat file' after CLUSTER?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group