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:35:56 |
Message-ID: | 45B8F88C.2080006@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> "Jeremy Haile" <jhaile(at)fastmail(dot)fm> writes:
>> Unfortunately I don't have any debugging tools installed that would work
>> against postgres - although I'd be glad to do something if you could
>> tell me the steps involved. I can reproduce the issue quite easily on
>> two different Windows machines (one is XP, the other is 2003).
>
> Sorry, I don't know anything about Windows debugging either. Can you
> put together a test case that would let one of the Windows-using hackers
> reproduce it?
That would help a lot.
>> Do you know of any workaround other than restarting the whole server?
>> Can the collector be restarted individually?
>
> On Unix you can just 'kill -TERM' the collector process and the postmaster
> will start a new one without engaging in a database panic cycle. Dunno
> what the equivalent is on Windows but it's probably possible.
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.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Smith | 2007-01-25 18:44:27 | Re: sequence increment jumps? |
Previous Message | Merlin Moncure | 2007-01-25 18:34:50 | Re: sequence increment jumps? |