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-09 17:12:50
Message-ID: 20090209171250.GB2870@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-02-09 17:18:31 Re: I can see beta now
Previous Message Tom Lane 2009-02-09 17:11:10 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS