Skip site navigation (1) Skip section navigation (2)

Re: Re: ps and psql from PostgreSQL not working with cygwin-1.1.5-2

From: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
To: cygwin <cygwin(at)sources(dot)redhat(dot)com>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: Re: Re: ps and psql from PostgreSQL not working with cygwin-1.1.5-2
Date: 2000-11-06 21:37:07
Message-ID: 20001106163707.A388@dothill.com (view raw or flat)
Thread:
Lists: pgsql-ports
Sorry for not letting this thread die...

On Sat, Nov 04, 2000 at 01:19:50AM +0100, Corinna Vinschen wrote:
> That's the problem. I thought about changing the behaviour of connect
> two weeks ago. I'm not sure if it makes sense to change the error code
> translation table for exactly that reason: Who knows what that would
> break? Perhaps it's better to change only the connect call to return
> EINPROGRESS. On the other hand Winsock seem to have interchanged the
> meaning of WOULDBLOCK and INPROGRESS (by mistake?). Hmmm.

Can some one very knowledgeable with socket programming (hopefully on
many platforms) please help us out?  Should socket clients (e.g., psql)
be expected to test errno for EWOULDBLOCK (a.k.a EAGAIN) when connect()
returns -1?  Or, should cygwin map EWOULDBLOCK to EINPROGRESS, at least
for connect()?

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corporation         Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

In response to

Responses

pgsql-ports by date

Next:From: lbottorffDate: 2000-11-06 21:40:46
Subject: RE: Errors building Postgres on NT
Previous:From: Chandra Sekhar . KDate: 2000-11-06 21:09:38
Subject: Has anybody compiled .c file generated from .pgc file

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group