X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 480D3D1C9BB; Fri, 23 Apr 2004 13:55:29 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 90052-05; Fri, 23 Apr 2004 13:55:26 -0300 (ADT)
Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171])
	by svr1.postgresql.org (Postfix) with ESMTP
	id BBCBBD1BAE9; Fri, 23 Apr 2004 13:55:25 -0300 (ADT)
Received: from ool-4352919e.dyn.optonline.net ([67.82.145.158]
	helo=matth.zeut.net) by outbound.mailhop.org with asmtp (Exim 4.20)
	id 1BH3xS-0009B9-UH; Fri, 23 Apr 2004 12:55:22 -0400
Received: from 192.154.91.225 (SquirrelMail authenticated user dbmail2user);
	by matth.zeut.net with HTTP; Fri, 23 Apr 2004 11:55:53 -0400 (EDT)
Message-ID: <47097.192.154.91.225.1082735753.squirrel@192.154.91.225>
In-Reply-To: <20040423124716.521420c2.darcy@druid.net>
References: <200404230409.i3N49jC02890@candle.pha.pa.us>
	<Pine.LNX.4.58.0404230935570.6454@sablons.cri.ensmp.fr>
	<58232.192.154.91.225.1082725121.squirrel@192.154.91.225>
	<1082732840.13948.45.camel@localhost.localdomain>
	<20040423124716.521420c2.darcy@druid.net>
Date: Fri, 23 Apr 2004 11:55:53 -0400 (EDT)
Subject: Re: [HACKERS] What can we learn from MySQL?
From: "Matthew T. O'Connor" <matthew@zeut.net>
To: "D'Arcy J.M. Cain" <darcy@druid.net>
Cc: pg@fastcrypt.com, matthew@zeut.net, coelho@cri.ensmp.fr,
	pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org,
	pgsql-advocacy@postgresql.org
User-Agent: SquirrelMail/1.5.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
X-Mail-Handler: MailHop Outbound by DynDNS.org
X-Report-Abuse-To: abuse@dyndns.org
X-MHO-User: Zeut
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0
	tests=PRIORITY_NO_NAME, RCVD_IN_NJABL, RCVD_IN_SORBS
X-Spam-Level: *
X-Archive-Number: 200404/222
X-Sequence-Number: 4194

> On Fri, 23 Apr 2004 11:07:20 -0400
> Dave Cramer <pg@fastcrypt.com> wrote:
>> Does the current implementation of pg_autovacuum have a way of setting
>> windows where it is allowed to vacuum? Many large 24/7 will only allow
>> vacuumming at certain times of the day.
>
> It seems to me that the point of pg_autovacuum would be to run 24/7 so
> that there is never big hit on the system.  Perhaps it could be designed
> to throttle itself based on current system usage though.

Right, there has been some talk about taking the system load into account,
but no action yet.

One comment I failed to make in my last email was that there should be
less need to explictly disallow vacuum during peak periods since vacuum
will only be occuring on specific tables when needed, which will effect
the server for a much smaller period of time than a general vacuum command
that touches all the tables.