From: Thomas Madsen <tm@softcom.dk>
To: pgsql-admin@postgresql.org
Subject: TOAST tables keeps growing!
Date: Thu, 12 Aug 2004 16:46:02 +0200
Message-ID: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local> (raw)
Hi.
I'm running a production server with PostgreSQL version 7.2.1, that does
email scans.
That means up to tens of thousands of entries in the database (log and
quarantine) each day, and an equal amount removed every night.
The problem is that TOAST tables keeps springing forth and consume disk
space.
We do a VACUUM every night, but it does not reduce or stop the TOAST
table growth.
I searched the mailing list for answers to this problem, but found only
other people describing the same problem.
Namely, that their max_fsm_pages were too low and that postgresql now
has lost track of the surplus TOAST data pages.
In our postgresql.conf we ourselves had the default value of 10000 for
max_fsm_pages, which I have now raised to around a million.
I restarted psql and did a vacuum to see if that would reduce the disk
usage, but no change was seen.
So the question(s) is:
What can I do to reclaim the wasted TOAST diskspace?
Can I find and eliminate the lost TOAST tuples somehow?
Thanks!
Best regards,
Thomas M. Madsen.
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: tm@softcom.dk
Subject: Re: TOAST tables keeps growing!
In-Reply-To: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local>
References: <64F70386AE9AB64D8F36DD6FC355555E570F32@hal9000.softcom.local>
* 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