Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f54ITrE60405; Mon, 4 Jun 2001 14:29:53 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f54ITcR06678; Mon, 4 Jun 2001 14:29:38 -0400 (EDT) To: Bruce Momjian cc: jeff@jeffjohnson.net, pgsql-interfaces@postgresql.org, pgsql-docs@postgresql.org Subject: Re: [INTERFACES] libpq sockets on win32 In-reply-to: <200106041753.f54HrrU27542@candle.pha.pa.us> References: <200106041753.f54HrrU27542@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 04 Jun 2001 13:53:53 -0400" Date: Mon, 04 Jun 2001 14:29:38 -0400 Message-ID: <6675.991679378@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/2 X-Sequence-Number: 797 Bruce Momjian writes: >> This article describes the problem and work around. >> http://msdn.microsoft.com/library/psdk/winsock/ovrvw3_26ia.htm > I can't read that web site under Netscape. Comes up fine for me (maybe you need to turn off Javascript?) However, the advice on it seems to be written by someone who does not know the difference between a variable and a function :-(. Read with a large grain of salt. We already have a couple of #ifdef'd usages of WSAGetLastError() in libpq, but it's quite unclear which other references to errno might need to be changed. A blanket replacement of errno would certainly break things. regards, tom lane