"Tom Lane" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
