From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Unresolved Win32 bug reports |
Date: | 2006-04-20 17:59:28 |
Message-ID: | 20060420175928.GE49405@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 20, 2006 at 07:25:15PM +0200, Martijn van Oosterhout wrote:
> On Thu, Apr 20, 2006 at 12:17:07PM -0500, Jim C. Nasby wrote:
> > Here's one to add to the list: running pgbench with a moderately heavy
> > load on an SMP box likes to trigger a state where the database (or
> > pgbench) just stops doing work (CPU usage drops to nothing, as does disk
> > activity). I've been able to repro this on 2 Intel boxes (one a 2 way,
> > one a 4 way), and a dual Opteron, all running the latest windows binary.
> > A 50 connection test running 1000 transactions is pretty much ensured to
> > fail.
>
> Well, this sounds like a dead-lock, the obvious step would be to
> attached gdb to both and get a stack-trace...
Any pointers on how to get that setup? IS gdb part of the mingw runtime?
BTW, this appears to be readily reproducable, so it might be a lot more
productive for one of the windows hackers to test this themselves...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-20 18:00:19 | Re: Unresolved Win32 bug reports |
Previous Message | Tom Lane | 2006-04-20 17:55:21 | Re: pg_dump -Ft failed on Windows XP |