Re: SO_SNDBUF size is small on win32? - Mailing list pgsql-hackers

From Yoshiyuki Asaba
Subject Re: SO_SNDBUF size is small on win32?
Date
Msg-id 20060628.014337.41652237.y-asaba@sraoss.co.jp
Whole thread Raw
In response to Re: SO_SNDBUF size is small on win32?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SO_SNDBUF size is small on win32?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [HACKERS] SO_SNDBUF size is small on win32? 
Date: Tue, 27 Jun 2006 12:28:35 -0400

> Andrew Dunstan <andrew@dunslane.net> writes:
> > Martijn van Oosterhout wrote:
> >> On Wed, Jun 28, 2006 at 12:23:13AM +0900, Yoshiyuki Asaba wrote:
> >>> http://support.microsoft.com/kb/823764/EN-US/
> 
> > No, it says it occurs if this condition is met: "A single *send* call or 
> > *WSASend* call fills the whole underlying socket send buffer."
> 
> It also says that the condition only occurs if the program uses
> non-blocking sockets ... which the backend does not.  So this page
> offers no support for the proposed patch.

WSAEventSelect() sets a socket to nonblocking mode.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50lrfWSAEventSelect.asp

pgwin32_send() calls pgwin32_waitforsinglesocket() before
WSASend(). And pgwin32_waitforsinglesocket() calls WSAEventSelect().

Regards,
--
Yoshiyuki Asaba
y-asaba@sraoss.co.jp


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Table clustering idea
Next
From: Csaba Nagy
Date:
Subject: Re: Table clustering idea