Re: TOAST tables keeps growing!

> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org
> [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: 13. august 2004 21:02
> To: Thomas Madsen
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] TOAST tables keeps growing!
>
>
> "Thomas Madsen" <tm(at)softcom(dot)dk> writes:
> > What can I do to reclaim the wasted TOAST diskspace?
>
> vacuum full might help.

Yes, vacuum full did the trick!

> > 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.

The bloating was primarily caused by the TOAST tables (several gigs
surplus), but the TOAST indexes are also slowly bloating as we have
indexes on a UNIX timestamp column. I will have to choose between
reindexing and upgrading...

For now I will keep an eye on the TOAST tables to see if the new FSM
value (1,000,000) keeps the TOAST tables at a reasonable size.

Thank you for the input!

Cheers,
Thomas.