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  LOG: autovacuum launcher shutting down
>>> 2008-08-25 04:00:01 EDT  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  LOG: received SIGHUP, reloading
2008-08-26 04:00:02 EDT  LOG: autovacuum launcher shutting down
2008-08-26 04:00:02 EDT  LOG: autovacuum launcher started
you can see the SIGHUP, the launcher being shut down, and starting right
back up again ???
is this expected behaviour ?
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2008-08-26 11:03:37|
|Subject: Re: Implementing cost limit/delays forinsert/delete/update/select|
|Previous:||From: Simon Riggs||Date: 2008-08-26 10:47:07|
|Subject: Re: Auto-explain patch|