Skip site navigation (1) Skip section navigation (2)

Signals on Win32 (was RE: [HACKERS] [PATCHES] fork/exec patch)

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
Cc: "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Signals on Win32 (was RE: [HACKERS] [PATCHES] fork/exec patch)
Date: 2003-12-18 19:05:57
Message-ID: 303E00EBDD07B943924382E153890E5434AA35@cuthbert.rcsinc.local (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Zeugswetter Andreas wrote:
> How about the typical answer on Windows ? Create an invisible Window
> with an Event Handler and pass it a windows message ?

The issue at hand is not how the signal is sent, but the behavior taken
once it arrives.  Using messages bypasses the thread problem but
requires PeekMessage() to be put in various places to check if there is
a signal waiting to be acted on, which is really any easier then
SleepEx(0), although, it does bypass the threading issues.

The other main issue with messages is that processes other than the
postmaster can issue them to a backend, which has some security
implications.  Also, there is a series of rather nasty exploits based on
WM_TIMER which have only been fixed in recent versions of windows.


pgsql-hackers-win32 by date

Next:From: Zeugswetter Andreas SB SDDate: 2003-12-19 10:00:47
Subject: Re: Signals on Win32 (was RE: [HACKERS] [PATCHES] fork/exec patch)
Previous:From: Zeugswetter Andreas SB SDDate: 2003-12-18 18:09:53
Subject: Re: [HACKERS] [PATCHES] fork/exec patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group