Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3B4BB632D13 for ; Thu, 5 Feb 2009 08:10:13 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 42336-08 for ; Thu, 5 Feb 2009 08:10:07 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mail.postgresql.org (Postfix) with ESMTP id 98954632D54 for ; Thu, 5 Feb 2009 08:10:06 -0400 (AST) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1LV33S-0001rY-G5 for pgsql-admin@postgresql.org; Thu, 05 Feb 2009 12:10:03 +0000 Received: from srv.protecting.net ([212.126.218.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Feb 2009 12:10:02 +0000 Received: from hari.fuchs by srv.protecting.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Feb 2009 12:10:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Harald Fuchs Subject: Re: autovacuum question Date: Thu, 05 Feb 2009 13:02:49 +0100 Lines: 17 Message-ID: References: <20090204165933.GB32680@alvh.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: srv.protecting.net X-Archive: encrypt User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Cancel-Lock: sha1:1QaxEEzgVi+en5y93LdcFWhlpPs= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200902/41 X-Sequence-Number: 31262 In article <20090204165933.GB32680@alvh.no-ip.org>, Alvaro Herrera writes: > Marc Mamin wrote: >> There are 2 features that would be helpfull in my case: >> >> - define vacuum properties on table groups rather than on given tables: >> >> For example, I don't want to vacuum daily tables which can be >> identified with a regexp: >> tablename ~ '\.*d_[0-9]{8}' > Hmm. I'm not really sure how could we handle this kind of situation. Couldn't we use schemas for that? Put all those tables into a separate schema and somehow tell autovacuum to leave that schema alone.