On Thu, Feb 5, 2009 at 7:13 PM, Robert Haas <robertmh...@gmail.com> wrote:
> 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).
In fact (he said to himself), we could take this a step further and
call both the reloption and GUC "autovacuum_policy". Then we could
have two policies for this release ("always" and "never") plus allow
"default" for the reloption. Then future releases could allow users
to define additional policies, like "off-hours".
Just thinking out loud here folks...
...Robert
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
