Received: from smtp02.mail.gol.com (smtp02.mail.gol.com [203.216.5.12])
	by hub.org (8.10.1/8.10.1) with ESMTP id e6DNgA068608
	for <pgsql-admin@postgresql.org>; Thu, 13 Jul 2000 19:42:10 -0400 (EDT)
Received: from wks02 (tc-2-178.ariake.gol.ne.jp [203.216.43.178])
	by smtp02.mail.gol.com (Postfix) with SMTP id 7648F1575B
	for <pgsql-admin@postgresql.org>; Fri, 14 Jul 2000 08:41:42 +0900 (JST)
From: "Rainer Mager" <rmager@vgkk.com>
To: <pgsql-admin@postgresql.org>
Subject: vacuum
Date: Fri, 14 Jul 2000 08:47:03 +0900
Message-ID: <NEBBJBCAFMMNIHGDLFKGCELPCDAA.rmager@vgkk.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <39350FEA.E1133121@ext.cri74.org>
Importance: Normal
X-Archive-Number: 200007/59

Hi all,

	I'm sure many other people have faced this and I'm wondering what solutions
were found.

	We have a product that uses PostgreSQL as its database. Currently, via a
web-based administration interface, we provide the administrators the
ability to vacuum their database whenever they wish to. We would prefer to
provide this functionality automatically such that they don't need to think
about it.
	We could easily have the system vacuum once a day (or week or whatever) but
we are concerned that the vacuum process will slow down the system while it
is being performed. This means that we would need to try to do some analysis
on the business of the system and then vacuum at a perceived slow time. This
sounds difficult.
	What do other people do? How much of a hit is vacuum when the system is
operating? Any other ideas?


Thanks in advance,

--Rainer