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

Re: Singnals code (not just win32 specific)

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Singnals code (not just win32 specific)
Date: 2004-01-22 13:34:35
Message-ID: 400FD16B.7050502@Yahoo.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
Magnus Hagander wrote:
> Hello!
> 
> The backend signals code today uses pqsignal() instead of signal() at
> all places. But it uses kill() and sigsetmask() (through the macro
> PG_SETMASK) directly.
> 
> I propose to change this to pqkill() and pqsigsetmask(). In pqsignal.h,
> these would be #define:d back to kill() and setsigmask() for the normal
> method, but would be functions on win32.

Sounds logical and more consistent than it is now.

While talking about it, I think our usage of signals is way overloaded 
anyway. Any ideas how to replace it all with just one signal and a 
regular message queue?


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #


In response to

Responses

pgsql-hackers by date

Next:From: Jan WieckDate: 2004-01-22 14:20:58
Subject: Re: cache control?
Previous:From: Thomas HallgrenDate: 2004-01-22 12:55:53
Subject: Dynamic modules and standard naming practice

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2004-01-22 14:59:51
Subject: What's left?
Previous:From: Magnus HaganderDate: 2004-01-22 09:54:10
Subject: Singnals code (not just win32 specific)

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