DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=k+ninr2agH9haOi5Qsg6PnZETEyP+Q3nxSsPB2qLNm8ebiKeu+Ue96PWQBL/tRQ4UWmc369xCsjp3Wa7m0jm1uL6vMW+q5qOrHRAwi5i6a6Q00cIvtNsFBmgm1Wz9xzPnrOW45WWxIEsA6EcB6L7wFMipj1H61r95IJKVkdWLCg=
Message-ID: <2e78013d0804171959k60d2f95ao5e735023433fbe43@mail.gmail.com>
Date: Fri, 18 Apr 2008 08:29:55 +0530
From: "Pavan Deolasee" <pavan.deolasee@gmail.com>
To: "Jesper Krogh" <jesper@krogh.cc>
Subject: Re: autovacuum?
Cc: pgsql-admin@postgresql.org
In-Reply-To: <4807A9A1.9040806@krogh.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4807A9A1.9040806@krogh.cc>

On Fri, Apr 18, 2008 at 1:18 AM, Jesper Krogh <jesper@krogh.cc> wrote:
>
>
>  So it seems to be running.

Yes.

> But shouldn't it hit the table a lot more?

That depends on your autovac settings, especially
autovacuum_vacuum_scale_factor. If it is set to 0.2 (which is
default), then autovacuum would hit the table whenever the percentage
of dead tuples is at least 20%. Again, the percentage of dead tuples
depends on your table size and rate of insert/update/delete.

>  How do I check that it is somehow near optimal?
>

Again that depends on how much table bloat you can sustain. If you
don't want the table to bloat too much, you can set aggressive
settings for autovac. But that would trigger autovac more often and
may have performance implication on your other concurrent queries.


Thanks,
Pavan

-- 
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com