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).
Please let me know if there is anything else I can do to help debug this
problem.
Do you know of any workaround other than restarting the whole server?
Can the collector be restarted individually?
Thanks,
Jeremy Haile
On Thu, 25 Jan 2007 12:42:11 -0500, "Tom Lane" <tgl@sss.pgh.pa.us> said:
> "Jeremy Haile" <jhaile@fastmail.fm> writes:
> > Did this information shed any light on what the problem might be?
>
> It seems to buttress Magnus' theory that the intermittent (or not so
> intermittent) stats-test buildfarm failures we've been seeing have to
> do with the stats collector actually freezing up, rather than just
> not reacting fast enough as most of us (or me anyway) thought. But
> why that is happening remains anyone's guess. I don't suppose you
> have debugging tools that would let you get a stack trace from the
> collector process?
>
> regards, tom lane
