Re: close() vs. closesocket()

Tom Lane wrote:
> mlw <pgsql@mohawksoft.com> writes:
> > Windows' sockets aren't very good.
> 
> They seem to be good enough that we have not had to worry about it,
> with the exception of the close/closesocket issue and the nonstandard
> error reporting mechanism.  But both of those have been worked around
> for a long time in the libpq sources.  Do we really need to insert a
> compatibility layer just to deal with those two problems?

Right.  The problem with a compatibility layer is that it adds another
level of abstraction.  That is not bad, but it might not make things
clearer either.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073