| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: can't stop autovacuum by HUP'ing the server |
| Date: | 2008-08-25 11:14:02 |
| Message-ID: | 16E81A65-0526-4685-BABE-7308EEE676CC@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24-Aug-08, at 10:12 PM, Tom Lane wrote:
> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> I'd like to stop autovac by changing the conf file then sending the
>> server a HUP
>
> Uh ... why should that stop an autovac already in progress? I'd
> only expect it to affect future launches.
>
Well, I go the extra mile and kill any remaing autovac procs
Here are the logs
2008-08-25 04:00:01 EDT [32276] LOG: autovacuum launcher shutting down
2008-08-25 04:00:01 EDT [20526] LOG: autovacuum launcher started
2008-08-25 04:00:01 EDT [21404] FATAL: terminating autovacuum
process due to administrator command
2008-08-25 04:00:01 EDT [23418] FATAL: terminating autovacuum
process due to administrator command
2008-08-25 04:00:01 EDT [21703] FATAL: terminating autovacuum
process due to administrator command
So now that I've read this why would the launcher start again ?
Dave
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2008-08-25 11:15:04 | Re: can't stop autovacuum by HUP'ing the server |
| Previous Message | Dimitri Fontaine | 2008-08-25 10:14:28 | Re: IN, BETWEEN, spec compliance, and odd operator names |