From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Subject: | Re: Open items |
Date: | 2004-08-16 17:12:37 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3412A745F@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sorry for the late reply, missed your initial response.
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> >> Does anyone have any more?
>
> > win32 signal safe socket handler
>
> I thought that was solved long ago?
As magnus wrote, we need to confirm that ssl sockets don't block singals
while waiting or they will not execute signals until a query runs.
> > win32 query cancel in psql (?)
>
> What's the issue here?
Win32 ctrl-c handler runs in a separate thread which ultimately calls
TerminateProcess(). Problem is does an immediate kill which does not
send the cancel signal to the backend. The solution is to install a
custom ctrl-c handler (in fact a patch was submitted to do this) which
fires the appropriate signal. However, this code runs a separate
thread...the original patch (by Luf) was rejected because it did not
address thread safety issues.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-08-16 18:41:03 | Re: COPY with column headings |
Previous Message | Bruce Momjian | 2004-08-16 17:09:58 | Re: Open items |