From: | "Dave Cramer" <pg(at)fastcrypt(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: can't stop autovacuum by HUP'ing the server |
Date: | 2008-08-26 10:59:38 |
Message-ID: | 491f66a50808260359j1b882195y360baca894340421@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 25, 2008 at 1:07 PM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
> On 25-Aug-08, at 10:43 AM, Alvaro Herrera wrote:
>
> Dave Cramer wrote:
>>
>> 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
>>>
>>
>> What did you SIGHUP, the launcher or postmaster? You need the latter.
>> The launcher should exit automatically at that time.
>>
>
> No, I am HUP'ing the postmaster then subsequently killing any autovacuums
> still around, which may be the problem.
>
> I may be killing the launcher prematurely. I'll try again tonight.
>
Ok, here are the logs from last night
2008-08-26 04:00:02 EDT [25407] LOG: received SIGHUP, reloading
configuration files
2008-08-26 04:00:02 EDT [22649] LOG: autovacuum launcher shutting down
2008-08-26 04:00:02 EDT [30438] LOG: autovacuum launcher started
you can see the SIGHUP, the launcher being shut down, and starting right
back up again ???
is this expected behaviour ?
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-08-26 11:03:37 | Re: Implementing cost limit/delays for insert/delete/update/select |
Previous Message | Simon Riggs | 2008-08-26 10:47:07 | Re: Auto-explain patch |