Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id 632DF9FB25F;
	Sun, 15 Oct 2006 06:53:06 -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 67281-10; Sun, 15 Oct 2006 09:53:02 +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 E1FD89FA4F4;
	Sun, 15 Oct 2006 06:53:01 -0300 (ADT)
Received: by lynet.oppetid.no (Postfix, from userid 1019)
	id 6D7B0119EA7; Sun, 15 Oct 2006 11:52:59 +0200 (CEST)
Date: Sun, 15 Oct 2006 11:52:59 +0200
From: Tobias Brox <tobias@nordicbet.com>
To: "Matthew T. O'Connor" <matthew@zeut.net>
Cc: Csaba Nagy <nagy@ecircle-ag.com>, Edoardo Ceccarelli <eddy@axa.it>,
	postgres performance list <pgsql-performance@postgresql.org>,
	pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
Message-ID: <20061015095259.GA24002@oppetid.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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: 200610/97
X-Sequence-Number: 23400

[Matthew T. O'Connor - Wed at 02:33:10PM -0400]
> In addition autovacuum respects the work of manual or cron based 
> vacuums, so if you issue a vacuum right after a daily batch insert / 
> update, autovacuum won't repeat the work of that manual vacuum.

I was experimenting a bit with autovacuum now.  To make the least effect
possible, I started with a too high cost_delay/cost_limit-ratio.  The
effect of this was that autovacuum "never" finished the transactions it
started with, and this was actually causing the nightly vacuum to not do
it's job good enough.