Re: [BUGS] [HACKERS] Postgres process invoking exit resulting insh-QUIT core - Mailing list pgsql-bugs

From Peter J. Holzer
Subject Re: [BUGS] [HACKERS] Postgres process invoking exit resulting insh-QUIT core
Date
Msg-id 20170710201715.GB20216@hjp.at
Whole thread Raw
In response to Re: [BUGS] [HACKERS] Postgres process invoking exit resulting in sh-QUIT core  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-bugs
On 2017-07-07 15:25:07 +0800, Craig Ringer wrote:
> Can't immediately explain the exit code, and SIGQUIT should _not_ generate a
> core file.

Yes, it should. The default action of SIGQUIT is to terminate the
process with a core file.

From signal(7):

|      First the signals described in the original POSIX.1-1990 standard.
|
|      Signal     Value     Action   Comment
|      ──────────────────────────────────────────────────────────────────────
|      SIGHUP        1       Term    Hangup detected on controlling terminal
|                                    or death of controlling process
|
|      SIGINT        2       Term    Interrupt from keyboard
|      SIGQUIT       3       Core    Quit from keyboard
|      SIGILL        4       Core    Illegal Instruction
...

You can also easily test this by pressing Ctrl-\ in the shell while a
program is running:

% sleep 10
^\zsh: quit (core dumped)  sleep 10
%
       hp

--   _  | Peter J. Holzer    | we build much bigger, better disasters now
|_|_) |                    | because we have much more sophisticated
| |   | hjp@hjp.at         | management tools.
__/   | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] Deferrable constraint execution not respecting "initially immediate"?
Next
From: Amit Langote
Date:
Subject: Re: [BUGS] BUG #14738: ALTER SERVER for foregin servers not working