Re: new GUC var: autovacuum_process_all_tables

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new GUC var: autovacuum_process_all_tables
Date: 2009-02-06 17:20:28
Message-ID: 20090206172028.GA3089@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:

> I can't imagine, nor have I encountered in the 3 years of consulting I
> did since Autovaccum became available, such a use case.

Ok, so due to popular demand, I'm not implementing this new GUC.

> On the other hand, I'd been keen on a runtime suset autovaccum=on/off
> which we could call from a cron job or the pgadmin scheduler in order to
> have maintenance windows. Unless that's already becoming possible?

autovacuum=on/off is already SIGHUP as of 8.3 (not SUSET, since it makes
no sense to change it in a single connection).

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-02-06 17:24:11 Re: per-database locale: createdb switches
Previous Message Bruce Momjian 2009-02-06 17:13:21 Re: [COMMITTERS] pgsql: Implement prefetching via posix_fadvise() for bitmap index scans.