diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-20 12:57:17 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-20 12:57:17 -0500 |
| commit | 71b121f425486c2a02f88f90e2a7c852182b5af0 (patch) | |
| tree | e28b6bf902b883b74d6fffbb5583febf000c6b97 /src/backend/executor/execProcnode.c | |
| parent | fd436bba01f6df843a9f421669c02e2b970fdc7a (diff) | |
| download | postgresql-71b121f425486c2a02f88f90e2a7c852182b5af0.tar.gz postgresql-71b121f425486c2a02f88f90e2a7c852182b5af0.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/execProcnode.c')
0 files changed, 0 insertions, 0 deletions