Re: new GUC var: autovacuum_process_all_tables - Mailing list pgsql-hackers

From Robert Haas
Subject Re: new GUC var: autovacuum_process_all_tables
Date
Msg-id 603c8f070902051333p346181b4h9bbc593c47454c3e@mail.gmail.com
Whole thread Raw
In response to new GUC var: autovacuum_process_all_tables  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Thu, Feb 5, 2009 at 3:45 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Right now, when autovacuum is turned on we always assume it's supposed
> to process all tables except those that have autovacuum_enabled=false.
>
> Now, sometimes it might make more sense to keep it enabled but have it
> only check for certain tables, and leave the majority of them disabled.
> For this we'd have a separate GUC parameter, as in $SUBJECT (I'm not
> wedded to the name), and have the user set autovacuum_enabled=true via
> reloptions to enable it.
>
> Opinions?

Sounds horribly confusing.  It's not very difficult to write a script
to set this value for every table in the database, if that's what you
want to do.  Having autovacuum_enabled potentially mean two different
things depending on the value of some GUC sounds like a recipe for
confusion (and no I don't like it any better if we put the global
switch somewhere other than a GUC).

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: new GUC var: autovacuum_process_all_tables
Next
From: Alvaro Herrera
Date:
Subject: Re: new GUC var: autovacuum_process_all_tables