Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit10095ca

Browse files
committed
Log a message when resorting to SIGKILL during shutdown/crash recovery.
Currently, no useful trace is left in the logs when the postmasteris forced to use SIGKILL to shut down children that failed to respondto SIGQUIT. Some questions were raised about how often that scenariohappens in the buildfarm, so let's add a LOG-level message showingthat it happened.Discussion:https://postgr.es/m/1850884.1599601164@sss.pgh.pa.us
1 parent6693a96 commit10095ca

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎src/backend/postmaster/postmaster.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1850,6 +1850,8 @@ ServerLoop(void)
18501850
(now-AbortStartTime) >=SIGKILL_CHILDREN_AFTER_SECS)
18511851
{
18521852
/* We were gentle with them before. Not anymore */
1853+
ereport(LOG,
1854+
(errmsg("issuing SIGKILL to recalcitrant children")));
18531855
TerminateChildren(SIGKILL);
18541856
/* reset flag so we don't SIGKILL again */
18551857
AbortStartTime=0;

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp