X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 117BC11F690E for ; Sun, 23 Apr 2006 23:26:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 52409-02 for ; Sun, 23 Apr 2006 23:26:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id D8CF911F60E5 for ; Sun, 23 Apr 2006 23:26:42 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id A4AAC30F25; Mon, 24 Apr 2006 04:26:43 +0200 (MET DST) From: "Qingqing Zhou" X-Newsgroups: pgsql.hackers Subject: Re: Unresolved Win32 bug reports Date: Mon, 24 Apr 2006 10:23:07 +0800 Organization: Hub.Org Networking Services Lines: 25 Message-ID: References: <200604201102.k3KB21H07902@candle.pha.pa.us> <20060420171707.GD49405@pervasive.com> <20060420172515.GE1984@svana.org> <26379.1145556019@sss.pgh.pa.us> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 To: pgsql-hackers@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/852 X-Sequence-Number: 82575 "Tom Lane" wrote > Martijn van Oosterhout writes: > > 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). > > > Well, this sounds like a dead-lock, the obvious step would be to > > attached gdb to both and get a stack-trace... > > Yeah, I wonder if it's related to that apparent bug Qingqing saw in the > windows semaphore code? It's clearly windows-specific since no one's > ever reported any such thing on Unixen. > I also suspect the EAGAIN error reports are related to the semaphore code. So if possible, I suggest we patch the code and test it. Regards, Qingqing