diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-11 12:24:46 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-11 12:24:46 -0400 |
| commit | 10095ca634fb39d78cfae8000489a19f4f4e27ef (patch) | |
| tree | 97cf222707464bc4c04a66022fa7e1cafcee0d88 /src | |
| parent | 6693a96b329ec46f1df916f2a28d640cc9a9977d (diff) | |
| download | postgresql-10095ca634fb39d78cfae8000489a19f4f4e27ef.tar.gz postgresql-10095ca634fb39d78cfae8000489a19f4f4e27ef.zip | |
Log a message when resorting to SIGKILL during shutdown/crash recovery.
Currently, no useful trace is left in the logs when the postmaster
is forced to use SIGKILL to shut down children that failed to respond
to SIGQUIT. Some questions were raised about how often that scenario
happens in the buildfarm, so let's add a LOG-level message showing
that it happened.
Discussion: https://postgr.es/m/1850884.1599601164@sss.pgh.pa.us
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/postmaster/postmaster.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 081022a2065..3cd6fa30eb0 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -1850,6 +1850,8 @@ ServerLoop(void) (now - AbortStartTime) >= SIGKILL_CHILDREN_AFTER_SECS) { /* We were gentle with them before. Not anymore */ + ereport(LOG, + (errmsg("issuing SIGKILL to recalcitrant children"))); TerminateChildren(SIGKILL); /* reset flag so we don't SIGKILL again */ AbortStartTime = 0; |