I'll try to put together a test case for hackers, although I'm not sure
what exactly causes it.
Basically, when I fire up PostgreSQL - after about a minute the stats
collector runs once (pgstat.stat is updated, autovacuum fires up, etc.)
- and then the collector seems to hang. If I watch it's performance
information, it does not read or write to disk again and pgstat.stat is
never updated again. It never updates pgstat.stat more than once after
restart. There are no errors in the log
I tried killing the collector a variety of ways on Windows, but it seems
to terminate indefinitely. I don't see a kill program for windows that
lets me specify the signal to use. So other than restarting PostgreSQL,
I'm not sure how to workaround this problem.
If anyone else is experiencing similar problems, please post your
situation.
On Thu, 25 Jan 2007 12:51:31 -0500, "Tom Lane" <tgl@sss.pgh.pa.us> said:
> "Jeremy Haile" <jhaile@fastmail.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