X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id E1031D1C9DE for ; Tue, 5 Aug 2003 13:46:53 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 07537-05 for ; Tue, 5 Aug 2003 10:45:39 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id F1B0AD1C9D8 for ; Tue, 5 Aug 2003 10:46:41 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h75Dl1is005777 for ; Tue, 5 Aug 2003 19:17:01 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h75Dkxir005751 for ; Tue, 5 Aug 2003 19:17:00 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Tue, 05 Aug 2003 19:18:33 +0530 MIME-Version: 1.0 Subject: Re: Some vacuum & tuning help Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F300309.24908.A81164@localhost> In-reply-to: References: <3F2FF1E6.10579.651E89@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/61 X-Sequence-Number: 2878 On 5 Aug 2003 at 14:15, Peter Childs wrote: > On Tue, 5 Aug 2003, Shridhar Daithankar wrote: > > > On 5 Aug 2003 at 8:09, Jeff wrote: > > > > I would suggest autovacuum daemon which is in CVS contrib works for 7.3.x as > > well.. Or schedule a vacuum analyze every 15 minutes or so.. > > I've just got autovacum up and Since we have had a lot of talk > about it recently..... I thought some feed back might be useful. > It seams to work quite well. But can be rather zelous on its > analysing for the first few hours. Curretly its analysig static (ie > nothigs changed) tables every 10minites. Vacuums seam to be about right. > I think that many vacuums may be slowing does my database.... IIRC there is per operation threshold. If update threshold is 5% and table is 2% updatedit, then it should not look at it at all. It's worth mentioning that you should start auto vacuum daemon on a clean database. i.e. no pending vacuum. It is not supposed to start with a database which has lots of clean up pending. The essence of auto vacuum daemon is to maintain a clean database in clean state.. I agree, specifying per table thresholds would be good in autovacuum.. Bye Shridhar -- WYSIWYG: What You See Is What You Get.