Postgres Pro
Downloads
Home   >   mailing lists

Re: can't stop autovacuum by HUP'ing the server - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: can't stop autovacuum by HUP'ing the server
Date
Msg-id 491f66a50808260359j1b882195y360baca894340421@mail.gmail.com
Whole thread Raw
In response to Re: can't stop autovacuum by HUP'ing the server  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: can't stop autovacuum by HUP'ing the server  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Tree view


On Mon, Aug 25, 2008 at 1:07 PM, Dave Cramer <pg@fastcrypt.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

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Implementing cost limit/delays for insert/delete/update/select
Next
From: Benedek László
Date:
Subject: Re: pg_dump roles support