To: "Mindaugas Riauba" <mind@bi.lt>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to avoid database bloat 
In-reply-to: <018601c56744$9d5aae50$f20214ac@bite.lt> 
References: <00d501c5667d$8cc12320$f20214ac@bite.lt>
	<13878.1117636799@sss.pgh.pa.us>
	<018601c56744$9d5aae50$f20214ac@bite.lt>
Comments: In-reply-to "Mindaugas Riauba" <mind@bi.lt>
	message dated "Thu, 02 Jun 2005 10:28:03 +0300"
Date: Thu, 02 Jun 2005 09:45:39 -0400
Message-ID: <13178.1117719939@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Mindaugas Riauba" <mind@bi.lt> writes:
>> First thing I'd suggest is to get a more detailed idea of exactly
>> what is bloating --- which tables/indexes are the problem?

>   I think the most problematic table is this one. After vacuum full/reindex
> it was 20MB in size now (after 6 hours) it is already 70MB and counting.

AFAICT the vacuum is doing what it is supposed to, and the problem has
to be just that it's not being done often enough.  Which suggests either
an autovacuum bug or your autovacuum settings aren't aggressive enough.

Which PG version is this exactly?  Some of the earlier autovacuum
releases do have known bugs, so it'd be worth your while to update
if you're not on the latest point release of your series.

I don't know much about autovacuum settings, but if you'll show what
you're using someone can probably comment on them.

			regards, tom lane