Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2

From: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2
Date: 2005-10-03 15:17:56
Message-ID: BAYC1-PASMTP01A3A1FFA771B31B32E1FF95800@CEZ.ICE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

pg_stat_activity sometimes list no connections or a number of connections
much smaller than the number of postgres.exe processes.

We also have these messages in our PostgreSQL log approximately
20 times a day.

FATAL: could not read from statistics collector pipe: No error
FATAL: could not write to statistics collector pipe: No connection could be
made because the target machine actively refused it.

or

FATAL: could not read from statistics collector pipe: No error
LOG: statistics collector process (PID 1628) was terminated by signal 1

It looks like the pg_stat_activity problem and the messages become
more frequent as the load/number of connection increases.

We were having the same pg_stat_activity problem and the same messages
with PostgreSQL 8.0.1 but didn't have the messages with PostgreSQL 7.4.1.
we don't know if pg_stat_activity was ok with 7.4.1 because we weren't using
it back then.

We are using Windows 2000 Server, Service Pack 4.

Thanks
Jean-Pierre Pelletier
e-djuster

Browse pgsql-bugs by date

  From Date Subject
Next Message Jean-Pierre Pelletier 2005-10-03 16:21:09 Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2
Previous Message Tom Lane 2005-10-03 02:46:39 Re: BUG #1933: ADD COLUMN with DEFAULT resets table oids