aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-09-11 12:24:46 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-09-11 12:24:46 -0400
commit10095ca634fb39d78cfae8000489a19f4f4e27ef (patch)
tree97cf222707464bc4c04a66022fa7e1cafcee0d88 /src/backend/executor
parent6693a96b329ec46f1df916f2a28d640cc9a9977d (diff)
downloadpostgresql-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/backend/executor')
0 files changed, 0 insertions, 0 deletions