Message-ID: <4656C1C7.3000003@archonet.com>
Date: Fri, 25 May 2007 12:00:23 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
To: Bastian Voigt <post@bastian-voigt.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Problem with Vacuum of bytea table (PG
 8.0.13)
References: <46569E6A.2060509@bastian-voigt.de>
 <4656BB5E.3000109@archonet.com>
	<4656BEF1.4050609@bastian-voigt.de>
In-Reply-To: <4656BEF1.4050609@bastian-voigt.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bastian Voigt wrote:
> 
> OK, I'll give that a try. What about pg_autovacuum then? Is it a problem
> when two processes try to vacuum the same table in parallel? Or do I
> need to deactivate autovacuum altogether?

I was about to say that you can tune pg_autovacuum, but I just checked 
your original post and you're running 8.0.x - not sure about that one.

You'll have to check the documentation for that version to see if you 
can either:
1. exclude that table from pg_autovacuum
2. increase pg_autovacuum's sensitivity

If not, and this table is the most active, it might be simpler just to 
run your own vacuum-ing from a cron job.

-- 
   Richard Huxton
   Archonet Ltd