| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new GUC var: autovacuum_process_all_tables |
| Date: | 2009-02-09 17:37:17 |
| Message-ID: | 17309.1234201037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Josh Berkus wrote:
>> 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?
Like, say, pg_reload_conf()? But actually a cron job would almost
certainly find it more pleasant to use pg_ctl reload and never bother
with a database connection at all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2009-02-09 17:41:25 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Previous Message | Tom Lane | 2009-02-09 17:32:54 | Re: I can see beta now |