From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Jim C. Nasby <jnasby@pervasive.com>
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 14:00:19 -0400
Message-ID: <26379.1145556019@sss.pgh.pa.us> (raw)
In-Reply-To: <20060420172515.GE1984@svana.org>
References: <200604201102.k3KB21H07902@candle.pha.pa.us>
<20060420171707.GD49405@pervasive.com>
<20060420172515.GE1984@svana.org>
Martijn van Oosterhout <kleptog@svana.org> 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
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: tgl@sss.pgh.pa.us, kleptog@svana.org, jnasby@pervasive.com, pgman@candle.pha.pa.us
Subject: Re: Unresolved Win32 bug reports
In-Reply-To: <26379.1145556019@sss.pgh.pa.us>
* 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