Erik Walthinsen <omega@temple-baptist.com> writes:
> Apr 22 04:00:02 alpha postgres[362]: [1] DEBUG: statistics collector
> process (pid 364) exited with exit code 1
> Apr 22 04:00:02 alpha postgres[362]: [2] DEBUG: statistics collector
> process (pid 17945) exited with exit code 1
> . . . .
> Apr 22 04:16:32 alpha postgres[362]: [445836] DEBUG: statistics collector
> process (pid 1629) exited with exit code 1
> The machine is a stock Debian Woody box, up to date, with no local changes
> to the postgres configuration at all. It's running 7.2.1-2woody2.
Hmm. Evidently the pgstat subprocess is dying immediately on launch.
Checking the archives, I see that back then pgstat was in the habit of
reporting its woes on stderr no matter what the elog destination was
supposed to be :-(. So the actually useful message went to postmaster
stderr, which more than likely is routed to /dev/null by your postmaster
startup script.
If you want to try to figure out what went wrong, you could alter the
start script to enable collection of stderr output and then try to
reproduce the problem.
regards, tom lane
