On Thu, 2009-02-05 at 17:45 -0300, Alvaro Herrera wrote: > Hi, > > 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? >
So you are inverting the option? What I mean is you are giving the option of either: A. Process everything unless false B. Process nothing unless true If I am understanding what you wrote correctly I am not sure I like the idea as a whole. I think we should just always have it on and not have it be optional. The rule of thumb should be, we autovacuum everything, unless there is a extremely good reason not to and I think you should have to explicitly turn off autovacuum for a relation. Sincerely, Joshua D. Drake > -- > Alvaro Herrera http://www.CommandPrompt.com/ > PostgreSQL Replication, Consulting, Custom Development, 24x7 support > -- PostgreSQL - XMPP: jdr...@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
