X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 89ED611F662E for ; Wed, 12 Apr 2006 12:16:03 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.254 X-Spam-Level: X-Spam-Status: No, score=0.254 required=5 tests=[AWL=0.945, BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2, DNS_FROM_RFC_POST=1.708] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id 2WHu8wNlJ9+G for ; Wed, 12 Apr 2006 12:15:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx3.surnet.cl (mx3.surnet.cl [216.155.73.182]) by postgresql.org (Postfix) with ESMTP id CF57D11F68FF for ; Wed, 12 Apr 2006 12:15:55 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx3.surnet.cl with ESMTP; 12 Apr 2006 11:15:54 -0400 X-IronPort-AV: i="4.04,115,1144036800"; d="scan'208"; a="3965108:sNHT89263094" Received: from alvh.no-ip.org (201.221.200.14) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 443B7DDC00036987; Wed, 12 Apr 2006 11:15:53 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 925DAC2DC22; Wed, 12 Apr 2006 11:15:53 -0400 (CLT) Date: Wed, 12 Apr 2006 11:15:53 -0400 From: Alvaro Herrera To: Chris Hoover Cc: Anthony Ransley , "pgsql-admin@postgresql.org" Subject: Re: Autovacuum ideas Message-ID: <20060412151553.GD23855@surnet.cl> Mail-Followup-To: Chris Hoover , Anthony Ransley , "pgsql-admin@postgresql.org" References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com> <443C39ED.6050706@aurema.com> <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> User-Agent: Mutt/1.5.11+cvs20060330 X-Archive-Number: 200604/109 X-Sequence-Number: 21278 Chris Hoover wrote: > This is what we are doing today (except we are on Linux :) ). However, > since there is talk of making autovacuum on by default and the advantages of > having it run, it would be nice to be able to block out hours that it can > not run. It would also be very nice to have the database take care of all > of this via the config file and/or tables. That way, no external programs > (cron or what ever) would be needed. > > Even nicer would be to have the time exclusion granular enough to be table > to exclude only certain tables. That way autovacuum can do it's work as > needed on the majority of the tables, but tables that the DBA knows will > cause problems during business hours could be excluded until the slow time. > > Any comments on this? I don't think autovacuum will be on by default until we have a way to configure rush hours, maintenance windows, etc. The system I envision has tables grouped in some way, and maintenance windows would operate on table groups. For example you will be able to include the fat table in a (possibly otherwise empty) group, and have that group not be processed during "work hours"; the rest of the tables would continue to be vacuumed at all times. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support