RE: Cygwin PostgreSQL Regression Test Problems (Revisited) - Mailing list pgsql-ports

From Hiroshi Inoue
Subject RE: Cygwin PostgreSQL Regression Test Problems (Revisited)
Date
Msg-id EKEJJICOHDIEMGPNIFIJOEBIEAAA.Inoue@tpf.co.jp
Whole thread Raw
In response to Re: Cygwin PostgreSQL Regression Test Problems (Revisited)  (Jason Tishler <Jason.Tishler@dothill.com>)
Responses Re: Cygwin PostgreSQL Regression Test Problems (Revisited)
List pgsql-ports
> -----Original Message-----
> From: Jason Tishler
>
> Tom,
>
> On Fri, Mar 30, 2001 at 09:25:47AM -0500, Jason Tishler wrote:
> > Any feedback on my patch (reattached for convenience)?  I would hate to
> > see 7.1 go out the door with this issue.
>
> I believe that I have finally found the root cause to the psql hangs.
> IMO, Cygwin is functioning properly and the issue lies in the libpq's
> pqWait() use of select().
>
> The MSDN states the following for select():
>
> ..
> Summary:
>     A socket will be identified in a particular set when select
> returns if:
>
> ..
>
> exceptfds:
>     If processing a connect call (nonblocking), connection
> attempt failed.
> ..
>

Oh I found the same description yesterday though I've had no time
to test it. If your patch resolves *hang*, it may be the right solution
at least for cygwin port.
BTW I've never passed the pararell regression test without hang or
refusal(with your previous patch appiled) under my cygwin environ-
ment. I added one more connect() call after the refusal and passed
all regression test successfully. Hmm it may be a more preferable
solution.

regards,
Hiroshi Inoue

pgsql-ports by date:

Previous
From: Jason Tishler
Date:
Subject: Re: Cygwin PostgreSQL Regression Test Problems (Revisited)
Next
From: Tom Lane
Date:
Subject: Re: Cygwin PostgreSQL Regression Test Problems (Revisited)