Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
Date
Msg-id 12357.1197437450@sss.pgh.pa.us
Whole thread Raw
In response to Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]  ("Trevor Talbot" <quension@gmail.com>)
Responses Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
"Trevor Talbot" <quension@gmail.com> writes:
> On 12/11/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I dunno anything about how to fix the real problem (what's winsock error
>> 10004?),

> WSAEINTR, "A blocking operation was interrupted by a call to
> WSACancelBlockingCall."

Oh, then it's exactly the same thing as our bug #2829.

I opined in that thread that OpenSSL was broken because it failed to
treat this as a retryable case like EINTR.  But not being much of a
Windows person, that might be mere hot air.  Someone with a Windows
build environment should try patching OpenSSL to treat WSAEINTR
the same as Unix EINTR and see what happens ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Trevor Talbot"
Date:
Subject: Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
Next
From: Bruce Momjian
Date:
Subject: Re: There's random access and then there's random access