From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Madsen <tm@softcom.dk>
Cc: pgsql-admin@postgresql.org
Subject: Re: TOAST tables keeps growing!
Date: Fri, 13 Aug 2004 15:02:19 -0400
Message-ID: <25925.1092423739@sss.pgh.pa.us> (raw)
In-Reply-To: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local>
References: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local>
"Thomas Madsen" <tm@softcom.dk> writes:
> What can I do to reclaim the wasted TOAST diskspace?
vacuum full might help.
> Can I find and eliminate the lost TOAST tuples somehow?
Well, one thing to ask is whether it's the toast *table* that's
bloating, or the *index* on the toast table. (VACUUM VERBOSE
would help you find out.)
If it's the table, then more frequent plain vacuums and/or increasing
FSM should fix it. If the index is growing while the table stays
about the same, you could try periodic REINDEXes, but the only real
solution is to move up to PG 7.4.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, tm@softcom.dk
Subject: Re: TOAST tables keeps growing!
In-Reply-To: <25925.1092423739@sss.pgh.pa.us>
References: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local> <25925.1092423739@sss.pgh.pa.us>
* 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