Re: pg_stat_activity showing non-existent processes

Perhaps I might be able to help you track this problem down, but I could use
some help. The limited amount of discussion on this I Googled up didn't
help. We have never seen these messages before; we are assuming that their
appearance now (we have been running OK since last August) is related to two
recent changes we made to our Windows 2003 Server (SvcPk 1), PostgreSQL
8.0.4 installation:
(1) started capturing statistics with the following config parms; all
other parms
were installation defaults:
debug_pretty_print "on"
log_min_duration_statement "60"
log_min_error_statement "debug1"
log_statement "ddl"
log_truncate_on_rotation "on"
stats_block_level "on"
stats_command_string "on"
stats_reset_on_server_start "on"
stats_row_level "on"
stats_start_collector "on"
(2) added additional application workload to this server

Don't understand the 'target machine' message, either; in this case, we are
running the application and the database server on the same box.

2006-04-04 03:12:05 FATAL: could not read from statistics collector pipe:
No error 2006-04-04 03:12:06 FATAL: could not write to statistics collector
pipe: No connection could be made because the target machine actively
refused it.
2006-04-04 04:16:58 FATAL: could not read from statistics collector pipe:
No error 2006-04-04 04:16:58 FATAL: could not write to statistics collector
pipe: No connection could be made because the target machine actively
refused it.
2006-04-04 05:47:26 FATAL: could not read from statistics collector pipe:
No error 2006-04-04 05:47:27 LOG: statistics collector process (PID 1776)
was terminated by signal 1

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
Sent: Tuesday, April 04, 2006 1:29 AM
To: Kevin Grittner
Cc: Jerry Sievers; pgsql-admin(at)postgresql(dot)org; Peter Brant
Subject: Re: [ADMIN] pg_stat_activity showing non-existent processes

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> It is probably related to something we've been seeing in the PostgreSQL
> logs on the Windows servers:

> [2006-04-03 08:28:25.990 ] 2072 FATAL: could not read from statistics
> collector pipe: No error
> [2006-04-03 08:28:26.068 ] 2012 LOG: statistics collector process (PID
> 3268) was terminated by signal 1

We've heard reports of instability in the stats collector on Windows
before, though I'm not sure if this is exactly the symptom --- check
the list archives. Nobody's been able to track it down yet.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend