On Apr 4, 2006, at 1:29 AM, Tom Lane wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.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.
BTW, I was (attempting) to do some performance testing on windows
Sunday with pgbench and I was getting an error similar to that (sorry
for being so vague, but I'm ~2000 miles from that server right now).
This was on a database created with a scale factor of 40 running on a
dual Xeon with plain SCSI drives (base tables on a seperate drive
from pg_xlog) running on XP with SP1. Any attempt to run pgbench with
40 connections for more than about 50 transactions would result in
that error (as well as some other ugliness).
Based just on that limited experience it looks like the windows port
could use a lot more shaking out with pgbench. Perhaps it would be a
good idea to add pgbench to the buildfarm test.
--
Jim C. Nasby, Database Architect decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
--
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
