From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Open items |
Date: | 2004-08-16 16:59:53 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BFCE@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2004-08-16 17:07:06 | Re: Timezone for %t log_line_prefix |
Previous Message | Tom Lane | 2004-08-16 16:51:21 | Re: Calling PL functions with named parameters |