X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 77F949FB2C2 for ; Wed, 9 Aug 2006 15:24:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 18172-04 for ; Wed, 9 Aug 2006 15:24:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 425F09FB2C4 for ; Wed, 9 Aug 2006 15:24:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.177]) by svr4.postgresql.org (Postfix) with ESMTP id 8633A5AF02D for ; Wed, 9 Aug 2006 18:24:10 +0000 (GMT) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout07/MantshX 4.0) with ESMTP id k79IO8B0021031 for ; Wed, 9 Aug 2006 11:24:08 -0700 (PDT) Received: from [192.168.0.9] ([206.135.69.99]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id k79IO5X5013852 for ; Wed, 9 Aug 2006 11:24:06 -0700 (PDT) Mime-Version: 1.0 Message-Id: Date: Wed, 9 Aug 2006 11:24:03 -0700 To: pgsql-admin@postgresql.org From: Joel Stevenson Subject: vacuumdb exclude tables option? Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.315 tagged_above=0 required=5 tests=SARE_MILLIONSOF X-Spam-Level: X-Archive-Number: 200608/119 X-Sequence-Number: 22662 Hi, I have a database that includes both highly transactional tables and archive tables - OLTP and OLAP mixed together. Some of the archival tables, which only experience inserts and reads, not updates or deletes, contain many millions of rows and so they take a *long* time to vacuum. Is there currently any means to exclude only these tables from vacuumdb operations other than explicitly vacuuming all the other tables and explicity skipping the archival tables? If not, are there any plans to add a command line switch to vacuumdb to exclude tables from it's operation, ala 'vacuumdb -d mytest -x archive_tab1 -x archive_tab2 -x archive_tab3'? I searched the list archives but didn't see anything about being able to do this. Something like this would save many hours of useless vacuuming in this particular setup. TIA, Joel