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 603c8f070902051613j677439f1p7e43eeb37d99ac34@mail.gmail.com
Whole thread Raw
In response to Re: new GUC var: autovacuum_process_all_tables  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: new GUC var: autovacuum_process_all_tables
List pgsql-hackers
>> Agreed, let's get this capability out in 8.4 and we can always adust it
>> based on user demand.
>
> Oh, I agree to limiting what we do for 8,4, but we need more later.

Thinking about this a little more, the biggest problem I have with
this feature is that it makes autovacuum_enabled mean two different
things depending on context.  But maybe we should change the name of
the reloption to "autovacuum" and have three values for it:
default|enabled|disabled.

Then we could add a GUC called autovacuum_by_default = on|off, and we
could later insert per-schema or per-database or per-table-group
defaults without introducing any backwards-incompatibility (default
would still mean default, though the default might come from a
different source).

...Robert


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: new GUC var: autovacuum_process_all_tables
Next
From: Andrew Dunstan
Date:
Subject: Re: new GUC var: autovacuum_process_all_tables