X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 264EE11F7D2F for ; Thu, 20 Apr 2006 14:59:44 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.431 X-Spam-Level: X-Spam-Status: No, score=-2.431 required=5 tests=[AWL=0.168, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id zsDchGikTSXs for ; Thu, 20 Apr 2006 14:59:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 85D5A11F6711 for ; Thu, 20 Apr 2006 14:59:29 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 7E40156431; Thu, 20 Apr 2006 12:59:29 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 20 Apr 2006 12:59:28 -0500 Date: Thu, 20 Apr 2006 12:59:28 -0500 From: "Jim C. Nasby" To: Martijn van Oosterhout Cc: Bruce Momjian , PostgreSQL-development Subject: Re: Unresolved Win32 bug reports Message-ID: <20060420175928.GE49405@pervasive.com> References: <200604201102.k3KB21H07902@candle.pha.pa.us> <20060420171707.GD49405@pervasive.com> <20060420172515.GE1984@svana.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060420172515.GE1984@svana.org> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060420:kleptog@svana.org::AL0Hplvk0lwqOf3X:00000000000000000000 0000000000000000000000003jOK X-Hashcash: 1:20:060420:pgman@candle.pha.pa.us::hGoP9Rk8/95J8hPO:000000000000000 00000000000000000000000054M/ X-Hashcash: 1:20:060420:pgsql-hackers@postgresql.org::7FfZS/i38PxW72k0:000000000 00000000000000000000000000cC X-Archive-Number: 200604/743 X-Sequence-Number: 82466 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