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 17444D1C9ED for ; Tue, 5 Aug 2003 15:45:31 +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 17485-09 for ; Tue, 5 Aug 2003 12:44:11 -0300 (ADT) Received: from neuromancer.ctlno.com (unknown [208.13.35.90]) by svr1.postgresql.org (Postfix) with ESMTP id 1BA50D1C4E0 for ; Tue, 5 Aug 2003 12:45:20 -0300 (ADT) Received: from hplaptop (ool-4352919e.dyn.optonline.net [67.82.145.158]) by neuromancer.ctlno.com (8.11.6/8.11.2) with SMTP id h75Fs2R22304; Tue, 5 Aug 2003 10:54:02 -0500 Message-ID: <004901c35b68$8a9d8010$c202a8c0@hplaptop> From: "Matthew T. O'Connor" To: "Tom Lane" Cc: , "Christopher Browne" , References: <60el00jhyx.fsf@dev6.int.libertyrms.info> <000b01c35b63$22d748d0$c202a8c0@hplaptop> <22888.1060097705@sss.pgh.pa.us> Subject: Re: Some vacuum & tuning help Date: Tue, 5 Aug 2003 11:45:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/72 X-Sequence-Number: 2889 From: "Tom Lane" > "Matthew T. O'Connor" writes: > > I chose to leave pg_autovacuum simple and not add too many features because > > the core team has said that it needs to be integrated into the backend > > before it can be considered a core tool. > > I think actually it makes plenty of sense to enhance pg_autovacuum while > it's still contrib stuff. My guess is it'll be much less painful to > whack it around in minor or major ways while it's standalone code. > Once it's integrated in the backend, making significant changes will be > harder and more ticklish. So, now is precisely the time to be > experimenting to find out what works well and what features are needed. Fair point, my only concern is that a backend integrated pg_autovacuum would be radically different from the current libpq based client application. When integrated into the backend you have access to a lot of information that you don't have access to as a client. I know one goal I have for the backend version is to be based on the FSM and not require the stats collector since it has a measurable negative effect on performance. But in the more general sense of learning what features people want (exclusion lists, per table defaults etc) I agree the current version is a sufficient testing ground.