| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jeremy Haile" <jhaile(at)fastmail(dot)fm> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Stats collector frozen? |
| Date: | 2007-01-25 17:51:31 |
| Message-ID: | 21264.1169747491@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"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?
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2007-01-25 17:51:41 | Re: column limit |
| Previous Message | Isaac Ben | 2007-01-25 17:47:50 | Re: column limit |