Re: [HACKERS] signal weirdness - Mailing list pgsql-hackers

From Peter Galbavy
Subject Re: [HACKERS] signal weirdness
Date
Msg-id 19990329121712.A11678@office.knowledge.com
Whole thread Raw
In response to signal weirdness  (Peter Galbavy <Peter.Galbavy@knowledge.com>)
Responses Re: [HACKERS] signal weirdness
List pgsql-hackers
On Mon, Mar 29, 1999 at 11:03:49AM +0100, Peter Galbavy wrote:
> Oh, the result - the regression tests hang waiting for the postgres
> process to receive the SIGQUIT to abort transaction that never
> comes.

My quick fix has been to replace the kill() with a direct call
to siglongjmp() - not sure if this is safe, but it works. I
am being a pragmatist today.

I will try to get more debugging done on the signal problem at
some stage, but I seem to have a "working" solution.

Is their any reason not to replace the kill() with a longjmp()
in the long run - no pun intended.

Regards,
-- 
Peter Galbavy
Knowledge Matters Ltd
http://www.knowledge.com /http://www.wonderland.org/ http://www.literature.org/


pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Large objects error - expected a 'V' from the backend
Next
From: Oleg Bartunov
Date:
Subject: Re: [HACKERS] Locale patch (Greek locale and koi8-to-win1251 tests)