Magnus Hagander wrote:
> >>> Does anyone have any more?
> >
> >> win32 signal safe socket handler
> >
> >I thought that was solved long ago?
>
> If this is what I think it is (Merlin - please confirm), this relates to
> the SSL code only. And the issue is that there are (I think - haven't
> 100% verified it yet) paths in the SSL code that will block withou it
> being possible to deliver signals. The end result would be a query you
> can't cancel/backend you can't kill.
OK, I added an SSL mention:
o fix signal safe socket handler for SSL
>
> The non-SSL codepaths emulate blocking sockets using non-blocking ones
> that also listen on signals. This has not been done for SSL sockets yet.
OK.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
