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 B446AD1CB1D; Fri, 23 Apr 2004 13:51:50 -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 84780-10; Fri, 23 Apr 2004 13:51:49 -0300 (ADT)
Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 69784D1C9ED; Fri, 23 Apr 2004 13:51:48 -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 1BH3tw-0006pj-8l; Fri, 23 Apr 2004 12:51:44 -0400
Received: from 192.154.91.225 (SquirrelMail authenticated user dbmail2user);
	by matth.zeut.net with HTTP; Fri, 23 Apr 2004 11:52:14 -0400 (EDT)
Message-ID: <33854.192.154.91.225.1082735534.squirrel@192.154.91.225>
In-Reply-To: <1082732840.13948.45.camel@localhost.localdomain>
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>
Date: Fri, 23 Apr 2004 11:52:14 -0400 (EDT)
Subject: Re: [HACKERS] What can we learn from MySQL?
From: "Matthew T. O'Connor" <matthew@zeut.net>
To: pg@fastcrypt.com
Cc: "Matthew T. O'Connor" <matthew@zeut.net>,
	"Fabien COELHO" <coelho@cri.ensmp.fr>,
	"Bruce Momjian" <pgman@candle.pha.pa.us>,
	"PostgreSQL-development" <pgsql-hackers@postgresql.org>,
	"PostgreSQL advocacy" <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/223
X-Sequence-Number: 4195

> 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.

No the current implementation doesn't, but such a feature is in the works
(planned anyway).  What I was envisioning is the ability to set two
different sets of thresholds (peak / off peak).  If you demand zero
vacuuming during peak times, you could set that threshold to -1, or some
such setting.

FYI I wouldn't remcommend defaulting pg_autovacuum to on until it does
this, and a few more things that are also planned (see the archives).

Matthew