Re: new GUC var: autovacuum_process_all_tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new GUC var: autovacuum_process_all_tables
Date: 2009-02-05 21:33:51
Message-ID: 603c8f070902051333p346181b4h9bbc593c47454c3e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 5, 2009 at 3:45 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-02-05 21:40:14 Re: new GUC var: autovacuum_process_all_tables
Previous Message Tom Lane 2009-02-05 21:29:40 Re: new GUC var: autovacuum_process_all_tables