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 E147D11F65A5 for ; Thu, 20 Apr 2006 15:00:28 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.376 X-Spam-Level: X-Spam-Status: No, score=-2.376 required=5 tests=[AWL=0.225, BAYES_00=-2.599, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id ABVlPsMMptdX for ; Thu, 20 Apr 2006 15:00:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 8C37F11F6D5C for ; Thu, 20 Apr 2006 15:00:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3KI0JEY026380; Thu, 20 Apr 2006 14:00:19 -0400 (EDT) To: Martijn van Oosterhout cc: "Jim C. Nasby" , Bruce Momjian , PostgreSQL-development Subject: Re: Unresolved Win32 bug reports In-reply-to: <20060420172515.GE1984@svana.org> References: <200604201102.k3KB21H07902@candle.pha.pa.us> <20060420171707.GD49405@pervasive.com> <20060420172515.GE1984@svana.org> Comments: In-reply-to Martijn van Oosterhout message dated "Thu, 20 Apr 2006 19:25:15 +0200" Date: Thu, 20 Apr 2006 14:00:19 -0400 Message-ID: <26379.1145556019@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/744 X-Sequence-Number: 82467 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. regards, tom lane