From: Jim C. Nasby <jnasby@pervasive.com>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: Unresolved Win32 bug reports
Date: Thu, 20 Apr 2006 12:59:28 -0500
Message-ID: <20060420175928.GE49405@pervasive.com> (raw)
In-Reply-To: <20060420172515.GE1984@svana.org>
References: <200604201102.k3KB21H07902@candle.pha.pa.us>
<20060420171707.GD49405@pervasive.com>
<20060420172515.GE1984@svana.org>
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@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jnasby@pervasive.com, kleptog@svana.org, pgman@candle.pha.pa.us
Subject: Re: Unresolved Win32 bug reports
In-Reply-To: <20060420175928.GE49405@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox