Re: new GUC var: autovacuum_process_all_tables - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: new GUC var: autovacuum_process_all_tables
Date
Msg-id 20090209171250.GB2870@alvh.no-ip.org
Whole thread Raw
In response to Re: new GUC var: autovacuum_process_all_tables  (Josh Berkus <josh@agliodbs.com>)
Responses Re: new GUC var: autovacuum_process_all_tables
List pgsql-hackers
Josh Berkus wrote:

>>> 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).
>
> Right.  What I'm saying is that if it *didn't* require a sighup, then  
> users could cronjob starting and stopping Autovac themselves.

Hmm, I'm not sure I understand what you're suggesting.  Maybe what you
want is that we have a SQL-accesible function that sends SIGHUP to the
postmaster?


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: I can see beta now
Next
From: Tom Lane
Date:
Subject: Re: How to get SE-PostgreSQL acceptable