Re: Unresolved Win32 bug reports

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unresolved Win32 bug reports
Date: 2006-04-24 02:23:07
Message-ID: e2hd0p$1o3a$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote
> Martijn van Oosterhout <kleptog(at)svana(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-04-24 02:58:31 Re: Additional current timestamp values
Previous Message Michael Fuhr 2006-04-24 02:02:05 Index scans when bitmap scans disabled