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 0F5D9D1C9CF for ; Tue, 5 Aug 2003 15:06:50 +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 13867-08 for ; Tue, 5 Aug 2003 12:05:30 -0300 (ADT) Received: from neuromancer.ctlno.com (unknown [208.13.35.90]) by svr1.postgresql.org (Postfix) with ESMTP id CC417D1C932 for ; Tue, 5 Aug 2003 12:06:38 -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 h75FFKR21918; Tue, 5 Aug 2003 10:15:20 -0500 Message-ID: <000b01c35b63$22d748d0$c202a8c0@hplaptop> From: "Matthew T. O'Connor" To: , "Christopher Browne" Cc: References: <60el00jhyx.fsf@dev6.int.libertyrms.info> Subject: Re: Some vacuum & tuning help Date: Tue, 5 Aug 2003 11:06:22 -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/68 X-Sequence-Number: 2885 From: "Christopher Browne" > Shridhar Daithankar wrote: > > I agree, specifying per table thresholds would be good in autovacuum.. > > Which begs the question of what the future direction is for pg_autovacuum. This is a good question. > There would be some merit to having pg_autovacuum throw in some tables > in which to store persistent information As long as pg_autovacuum is either a contrib module, or not integrated into the backend, we can't do this. I don't think we should require that tables are added to your database in order to run pg_autovacuum, I have thought that a "helper table" could be used, this table, if found by pg_autovacuum would use it for per table defaults, exclusion list etc.... That way pg_autovacuum can run without a polluted database, or can be tuned. If pg_autovacuum in made official, moves out of contrib and becomes a core tool, then we can either add columns to some system catalogs to track this information or add a new system table. > All well and interesting stuff that could be worth implementing. > > But the usual talk has been about ultimately integrating the > functionality into the backend, making it fairly futile to enhance > pg_autovacuum terribly much. > > Unfortunately, the "integrate into the backend" thing has long seemed > "just around the corner." I think we should either: > a) Decide to enhance pg_autovacuum, or > b) Not. I have been talking about "integraging it into the backend" for a while, and I used to think it was "just around the corner" unfortunately, work schedule and my C skills have prevented me from getting anything useful working. If you would like to work on it, I would help as much as possible. 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. ps, please cc me as I'm not subscribed to the list.