Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id C21979FA2AD;
	Wed, 27 Sep 2006 13:13:34 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 49054-04; Wed, 27 Sep 2006 16:13:30 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from lynet.oppetid.no (oppetid.no [80.65.51.2])
	by postgresql.org (Postfix) with ESMTP id 79DB89FB289;
	Wed, 27 Sep 2006 13:13:30 -0300 (ADT)
Received: by lynet.oppetid.no (Postfix, from userid 1019)
	id 3389911AFB5; Wed, 27 Sep 2006 18:13:29 +0200 (CEST)
Date: Wed, 27 Sep 2006 18:13:29 +0200
From: Tobias Brox <tobias@nordicbet.com>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-performance@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
Message-ID: <20060927161329.GB25630@oppetid.no>
References: <451AA1FE.9050704@axa.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <451AA1FE.9050704@axa.it>
Organization: Group Nordicbet
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO
X-Spam-Level: 
X-Archive-Number: 200609/326
X-Sequence-Number: 23240

[Edoardo Ceccarelli - Wed at 06:08:30PM +0200]
> We also activated the autovacuum feature to give it a try and that's 
> were our problems started.
(...)
> How can I configure the vacuum to run after the daily batch insert/update?

I think you shouldn't use autovacuum in your case.

We haven't dared testing out autovacuum yet even though we probably
should, so we're running vacuum at fixed times of the day.  We have a
very simple script to do this, the most important part of it reads:

echo "vacuum verbose analyze;" | psql $DB_NAME > $logdir/$filename 2>&1