Received: from new-york.safe.ca (modemcable102.137-200-24.mtl.mc.videotron.net [24.200.137.102]) by hub.org (8.10.1/8.10.1) with ESMTP id e6E1xc096353 for ; Thu, 13 Jul 2000 21:59:38 -0400 (EDT) Received: (from jmp@localhost) by new-york.safe.ca (8.9.3/8.9.3) id VAA17005; Thu, 13 Jul 2000 21:59:29 -0400 From: Jean-Marc Pigeon Message-Id: <200007140159.VAA17005@new-york.safe.ca> Subject: Re: vacuum To: rmager@vgkk.com (Rainer Mager) Date: Thu, 13 Jul 2000 21:59:29 -0400 (EDT) Cc: pgsql-admin@postgresql.org In-Reply-To: from "Rainer Mager" at Jul 14, 2000 10:55:07 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200007/62 Bonjour Rainer Mager > > Good ideas except I think I wasn't clear. The system is a commercial product > with numerous individual customers. Each customer is somewhat unique and we > want to have the system capable of vacuuming automatically for all users. > > The thing is that some users might have systems that are used little in the > early morning but others might be very different. We would rather not do > usage statistic gathering/analysis if there was a better way. We have the same kind of application here. We vacuum according the load, if the load start to be "high" we vacuum ->earlier<-, ok there is a little penalty on users, but as soon the data-base is clean, the performance is dramaticaly improving and the load just drop. So instead to have user penalised for a long time, we just use it as a trigger to clean the base. (we do not want the user to vacuum at will) A bientot ========================================================================== Jean-Marc Pigeon Internet: Jean-Marc.Pigeon@safe.ca SAFE Inc. Phone: (514) 493-4280 Fax: (514) 493-1946 REGULUS, a real time accounting/billing package for ISP REGULUS' Home base <"http://www.regulus.safe.ca"> ==========================================================================