Обсуждение: Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2
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
How were you running 7.4? Under cygwin or on a different OS? On Mon, Oct 03, 2005 at 12:21:09PM -0400, Jean-Pierre Pelletier wrote: > 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 > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Re: Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2
От
"Jean-Pierre Pelletier"
Дата:
We were running 7.4 under Cygwin with Windows 2000 Service Pack 4. ----- Original Message ----- From: "Jim C. Nasby" <jnasby@pervasive.com> To: "Jean-Pierre Pelletier" <pelletier_32@sympatico.ca> Cc: <pgsql-bugs@postgresql.org> Sent: Monday, October 03, 2005 6:00 PM Subject: Re: [BUGS] Unreliable pg_stat_activity, Windows 2000, PostgreSQL 8.1 beta2 > How were you running 7.4? Under cygwin or on a different OS? > > On Mon, Oct 03, 2005 at 12:21:09PM -0400, Jean-Pierre Pelletier wrote: >> 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 >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 9: In versions below 8.0, the planner will ignore your desire to >> choose an index scan if your joining column's datatypes do not >> match >> > > -- > Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com > Pervasive Software http://pervasive.com work: 512-231-6117 > vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461