>>> 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. 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. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
