Re: [HACKERS] [PATCHES] fork/exec patch
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] [PATCHES] fork/exec patch |
Дата | |
Msg-id | 28280.1071676565@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCHES] fork/exec patch ("Magnus Hagander" <mha@sollentuna.net>) |
Список | pgsql-hackers-win32 |
"Magnus Hagander" <mha@sollentuna.net> writes: > The difference is that if you fire the entire signal handler on the > different thread, which means they can execute concurrently. That won't > happen on Unix AFAIK - the main executino is stopped, right? So the > "main thread" could change a variable while the signal handler is still > executing - this can never happen in Unix when the signal handler > executes, because the main thread is stopped? Hm, good point. There probably are some issues there for the more complex signal handlers; they definitely assume nothing is changing underneath them. > An option would be to SuspendThread() on the main thread, which freezes > it completely durnig the execution of the signal. If necessary, are we > safe against that? (Basically, SuspendThread() will suspend a thread > even if it's inside a kernel call. Why would that be a problem? regards, tom lane
В списке pgsql-hackers-win32 по дате отправления: