Re: Stats collector frozen?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-general(at)postgresql(dot)org
Subject: Re: Stats collector frozen?
Date: 2007-01-25 18:44:33
Message-ID: 22284.1169750673@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2007-01-25 18:45:45 Re: Stats collector frozen?
Previous Message Benjamin Smith 2007-01-25 18:44:27 Re: sequence increment jumps?