From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Stats collector frozen? |
Date: | 2007-01-25 18:45:45 |
Message-ID: | 45B8FAD9.2030502@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> "Jeremy Haile" <jhaile(at)fastmail(dot)fm> writes:
>>>> Do you know of any workaround other than restarting the whole server?
>>>> Can the collector be restarted individually?
>
>> You can use pg_ctl to send the int signal. If it's completely hung, that
>> may not work. In that case you can kill it from task manager, but that's
>> equiv of a kill -9, which means that the postmaster will restart all
>> backends.
>
> No, the postmaster does not care how badly the stats collector croaks,
> because the collector's not connected to shared memory, so there's no
> risk of collateral damage. It'll just start a new one without bothering
> the backends. So you can do whatever you have to do to kill the stuck
> collector --- I was just not sure how to do that under Windows.
Oh, ok.
Then just pick it up in Task Manager or Process Explorer or whatever and
kill it off. Just make sure you pick the right process.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Smith | 2007-01-25 18:47:25 | Re: Converting 7.x to 8.x |
Previous Message | Tom Lane | 2007-01-25 18:44:33 | Re: Stats collector frozen? |