From: Qingqing Zhou <zhouqq@cs.toronto.edu>
To: pgsql-hackers@postgresql.org
Subject: Re: Unresolved Win32 bug reports
Date: Mon, 24 Apr 2006 10:23:07 +0800
Message-ID: <e2hd0p$1o3a$1@news.hub.org> (raw)
References: <200604201102.k3KB21H07902@candle.pha.pa.us>
<20060420171707.GD49405@pervasive.com>
<20060420172515.GE1984@svana.org>
<26379.1145556019@sss.pgh.pa.us>
"Tom Lane" <tgl@sss.pgh.pa.us> wrote
> 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.
>
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
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: zhouqq@cs.toronto.edu
Subject: Re: Unresolved Win32 bug reports
In-Reply-To: <e2hd0p$1o3a$1@news.hub.org>
* 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