Date: Thu, 5 Feb 2009 15:27:37 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Harald Fuchs <hari.fuchs@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum question
Message-ID: <20090205182737.GD2978@alvh.no-ip.org>
References: 
 <C4DAC901169B624F933534A26ED7DF311D5398@JENMAIL01.ad.intershop.net>
	<20090204165933.GB32680@alvh.no-ip.org>
	<pu7i459jme.fsf@srv.protecting.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <pu7i459jme.fsf@srv.protecting.net>
User-Agent: Mutt/1.5.18 (2008-05-17)

Harald Fuchs escribió:
> In article <20090204165933.GB32680@alvh.no-ip.org>,
> Alvaro Herrera <alvherre@commandprompt.com> 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:

> > 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.

I don't like that.  It would force the users to use schemas in a certain
way, taking flexibility away from them.

In an old design for autovacuum "maintenance windows" (which were
promised for 8.2 and still haven't seen the light of day) we were
introducing "table groups" as a concept.  Sounds like something that
applies here too.  If you can attach a table to a group during creation,
you can decide its autovacuum schedule right there.  You should be able
to do something like

create table d_123 ( ... ) WITH (autovacuum_group = 'dont_ever_vacuum');

which means autovacuum automatically ignores that table.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support