From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: Seum-Lim Gan <slgan@lucent.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance, vacuum and reclaiming space, fsm
Date: Mon, 13 Oct 2003 14:55:22 +0530
Message-ID: <3F8A6F82.6030300@persistent.co.in> (raw)
In-Reply-To: <p05100301bbb01a5b6576@[192.168.10.43]>
References: <p05100301bbb01a5b6576@[192.168.10.43]>
Seum-Lim Gan wrote:
> I have a table that keeps being updated and noticed
> that after a few days, the disk usage has growned to
> from just over 150 MB to like 2 GB !
Hmm... You have quite a lot of wasted space there..
>
> I followed the recommendations from the various search
> of the archives, changed the max_fsm_relations, pages,
> keep doing vacuum like every minute while the
> table of interest in being updated. I kept
> watching the disk space usage and still noticed that
> it continues to increase.
That will help if your table is in good shape. Otherwise it will have little
effect particularly after such amount of wasted space.
> Looks like vacuum has no effect.
Its not that.
> I did vacuum tablename and don't intend to use
> the full option since it locks the table.
You got to do that. simple vacuum keeps a running instance of server clean. But
once dead tuples spill to disk, nothing but vacumm full can reclaim that space.
And don't forget, you got to reindex the indexes as well.
Once your table is in good shape, you can tune max_fsm_* and vacuum once a
minute. That will keep it good..
> I have 7.3.3 running in Solaris 9.
>
> Any recommendation ?
HTH
Shridhar
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: shridhar_daithankar@persistent.co.in, slgan@lucent.com
Subject: Re: Performance, vacuum and reclaiming space, fsm
In-Reply-To: <3F8A6F82.6030300@persistent.co.in>
* 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