Re: "pgbench -c 13" causes backend hangup.

From: Jason Tishler <jason(at)tishler(dot)net>
To: Yutaka tanida <yutaka(at)hi-net(dot)zaq(dot)ne(dot)jp>
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: "pgbench -c 13" causes backend hangup.
Date: 2001-09-17 16:12:00
Message-ID: 20010917121200.O2272@dothill.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

Yutaka,

On Mon, Sep 17, 2001 at 12:00:55AM +0900, Yutaka tanida wrote:
> (gdb) bt
> #0 0x77f827e8 in _libkernel32_a_iname ()
> #1 0x77e56a15 in _libkernel32_a_iname ()
> #2 0x77e56a3d in _libkernel32_a_iname ()
> #3 0x00538a5d in semop ()
> #4 0x004cf450 in IpcSemaphoreLock (semId=5250, sem=11, interruptOK=1 '\001')
> at ipc.c:426
> [snip]
>
> Hmm... , it it a cygipc probrem?

Agreed.

We have two options:

1. build a debuggable cygipc and continue debugging
2. wait for true Cygwin (server) support of System V IPC

Given the following:

http://sources.redhat.com/ml/cygwin-apps/2001-09/msg00017.html
http://www.cygwin.com/ml/cygwin-patches/2001-q3/msg00151.html

I'm leaning toward option #2 above.

FYI, Rob Collins is the developer that recently contributed significant
(and very well done) Cygwin pthreads support and appears to be really
cranking out the new Cygwin server (including System V IPC) functionality.

Jason

In response to

Browse pgsql-cygwin by date

  From Date Subject
Next Message Tony Culshaw 2001-09-18 11:47:23 Problem with ./configure script?
Previous Message Jason Tishler 2001-09-17 13:04:51 Re: processor going at 100%