On Wed, Mar 07, 2007 at 07:46:16AM +0100, Martijn van Oosterhout wrote: > On Tue, Mar 06, 2007 at 08:38:22PM +0200, andyk wrote: > > This error is returned by libpq, as a reaction on WSANOBUFS error > > from Windows Socket System. This means, applications tries to send much > > data, and system can't do it the same quickly. Possible, libpq should > > handle this error more carefully, and wait until all data will be send > > to the server. > > That's bizarre. If libpq is sending data too fast then the socket > library should block. The only possible thing lbpq can do is send it > again, which will just give the same error... busy loop. This is a > problem the socket library should handle for you. > > Incidently, according to this page: > > http://www.dispi.com/proxyplus/faq/articles/EN/art10002.htm > > The error relates to too many sockets, rather than out of memory. In > which case libpq really can't do anything about it. This points even more clearly to asking the standard questino for any network related stuff - are you running any personal firewall software (other than the one builtin to windows - that one is known not to be so troublesome), bandwidth limiters or antivirus that has network scanning fetures? If so, try uninstalling it (you can first try disabling it, but quite often you need to uninstall all the way). (It could still simply be increasing the number of connections too far, but a broken fw might cause the problem to show up even though it's not really there) //Magnus
