Re: Bugs in our Windows socket code - Mailing list pgsql-hackers

From james
Subject Re: Bugs in our Windows socket code
Date
Msg-id 4FB09DCC.5010404@mansionfamily.plus.com
Whole thread Raw
In response to Bugs in our Windows socket code  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> That is, if you request FD_WRITE events for a pre-existing socket with
> WSAEventSelect, you will not get one until the outbound network buffer has
> been filled and then has partially emptied.  (This is incredibly broken,
> but Microsoft evidently has no intention of fixing it.)

I think you should distinguish between 'broken' and 'not what I am used 
to'.  Microsoft have always had an edge triggered delivery here, rather 
than the level triggered delivery on BSD.  But WinSock is not BSD 
sockets.  If you want to remember what the state is, associate a flag 
with the socket.  Microsoft are very good at retaining compatibility, 
'fixing it' in your terms would be crass breakage.



pgsql-hackers by date:

Previous
From: Prakash Itnal
Date:
Subject: ERROR: catalog is missing 2 attribute(s) for relid 16584
Next
From: Simon Riggs
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?