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

RE: [DOCS] Re: libpq sockets on win32

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <jeff(at)jeffjohnson(dot)net>
Cc: <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: [DOCS] Re: libpq sockets on win32
Date: 2001-06-05 14:47:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
> > > I have done exactly that.  I assume fcntl(), ioctl(),
> > > select() use errno
> > > even if used on a socket, while getsockopt(), setsockopt(),
> > socket(),
> > > connect(), getsockname(), send(), recv() use WSAGetLastError.  Is
> > this
> > > list correct?
> > 
> > I don't know enough about such things.
> The web page wasn't clear about that.
No, that list is not correct.

1) select() can *only* be used on a socket in Windows, and it puts its
error info in WSAGetLastError().

2) ioctl() should *not* be used on sockets. Instead, ioctlsocket()
shuold be used. ioctlsocket() puts its error info in WSAGetLastError().
( (loads
fine in my Netscape, doesn't look all that good, but definitly readable)

3) fcntl() should *not* be used on sockets. ioctlsocket() again. 

Generaelly, all functions dealing with sockets use WSAGetLastError().
And sockets and file descriptors are *not* necessarily interchangable on

Note - this is Win32, *not* cygwin. Cygwin maps to errno, AFAIK.



pgsql-interfaces by date

Next:From: Kemin ZhouDate: 2001-06-05 18:16:33
Subject: difficulty building the C++ interface
Previous:From: Tom LaneDate: 2001-06-05 14:16:40
Subject: Re: query works in psql, but not thru JDBC

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