aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-01-20 12:57:17 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-01-20 12:57:17 -0500
commit4ea5cf403824e98932aa17c1c00f9c5241daf89d (patch)
tree50b47a79579599a80d97e438d0a31af6e9343f17 /src/backend/executor/nodeModifyTable.c
parentda7abcf0f475bfacc064210d15be9e6e31e873f9 (diff)
downloadpostgresql-4ea5cf403824e98932aa17c1c00f9c5241daf89d.tar.gz
postgresql-4ea5cf403824e98932aa17c1c00f9c5241daf89d.zip
Fix pg_dump's sigTermHandler() to use _exit() not exit().
sigTermHandler() tried to be careful to invoke only operations that are safe to do in a signal handler. But for some reason we forgot that exit(3) is not among those, because it calls atexit handlers that might do various random things. (pg_dump itself installs no atexit handlers, but e.g. OpenSSL does.) That led to crashes or lockups when attempting to terminate a parallel dump or restore via a signal. Fix by calling _exit() instead. Per bug #16199 from Raúl Marín. Back-patch to all supported branches. Discussion: https://postgr.es/m/16199-cb2f121146a96f9b@postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions