public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected] <[email protected]>
To: 'Tom Lane' <[email protected]>
Cc: [email protected] <[email protected]>
Subject: RE: SIGQUIT handling, redux
Date: Thu, 10 Sep 2020 02:56:37 +0000
Message-ID: <TYAPR01MB299062483CF0D6115B6918B5FE270@TYAPR01MB2990.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

From: Tom Lane <[email protected]>
> This is straying a bit from the stated topic of this thread, but ...
> I did some further looking around to see whether there were any
> unsafe signal handlers besides SIGQUIT ones.  The situation is not
> too awful, but I did find several issues not already mentioned
> in this thread:

Wow, your eyes catch this many issues.  (I was just wondering about one or two of them.)

I'm not sure if this is related, but I had been wondering if the following can be what it is now.


(1)
When logical replication is used, pg_ctl stop with the default fast mode emits the message about termination of logical replication launcher.  Although it's not FATAL or ERROR, but I was a bit startled when I saw this message for the first time.  Why should this message be emitted while nothing about other postmaster children are reported?  The logical rep launcher ignores SIGINT (SIG_IGN).

LOG:  received fast shutdown request
LOG:  aborting any active transactions
LOG:  background worker "logical replication launcher" (PID 10056) exited with exit code 1
LOG:  shutting down
LOG:  database system is shut down


(2)
When the physical standby stops, a FATAL message is output.  It may be annoying to the DBA that monitors messages with high severity.

LOG:  received fast shutdown request
LOG:  aborting any active transactions
FATAL:  terminating walreceiver process due to administrator command
LOG:  shutting down
LOG:  database system is shut down


(3)
When WaitLatch(EXIT_ON_POSTMASTER_DEATH) detects postmaster death, it calls proc_exit(1).  Can we call _exit(1) here likewise?


Regards
Takayuki Tsunakawa

view thread (21+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: RE: SIGQUIT handling, redux
  In-Reply-To: <TYAPR01MB299062483CF0D6115B6918B5FE270@TYAPR01MB2990.jpnprd01.prod.outlook.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox