Re: SIGCHLD handler in Postgres C function. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SIGCHLD handler in Postgres C function.
Date
Msg-id 22880.996532800@sss.pgh.pa.us
Whole thread Raw
In response to Re: SIGCHLD handler in Postgres C function.  (Bill Studenmund <wrstuden@zembu.com>)
Responses Re: SIGCHLD handler in Postgres C function.  (Bill Studenmund <wrstuden@zembu.com>)
Re: SIGCHLD handler in Postgres C function.  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bill Studenmund <wrstuden@zembu.com> writes:
> Looking at source on the web, I found:

> kernel/signal.c:1042

> * Note the silly behaviour of SIGCHLD: SIG_IGN means that the
> * signal isn't actually ignored, but does automatic child
> * reaping, while SIG_DFL is explicitly said by POSIX to force
> * the signal to be ignored.

Hmm, interesting.  If you'll recall, the start of this thread was a
proposal to change our backends' handling of SIGCHLD from SIG_IGN to
SIG_DFL (and get rid of explicit tests for ECHILD).  I didn't quite see
why changing the handler should make a difference, but above we seem to
have the smoking gun.

Which kernel, and which version, is the above quote from?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bill Studenmund
Date:
Subject: Re: SIGCHLD handler in Postgres C function.
Next
From: Tom Lane
Date:
Subject: Re: SIGCHLD handler in Postgres C function.