Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core

From: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core
Date: 2017-07-10 20:17:15
Message-ID: 20170710201715.GB20216@hjp.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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(at)hjp(dot)at | management tools.
__/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2017-07-11 01:23:05 Re: BUG #14738: ALTER SERVER for foregin servers not working
Previous Message Tom Lane 2017-07-10 17:25:10 Re: Deferrable constraint execution not respecting "initially immediate"?

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-07-10 20:23:46 Re: RFC: Key normalization for nbtree
Previous Message Claudio Freire 2017-07-10 19:53:57 Re: RFC: Key normalization for nbtree