aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2018-08-08 19:08:10 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2018-08-08 19:09:35 +0300
commitf318f7fdf85a269ed652e16f67015c3dde960754 (patch)
tree65510a23d9b1293dc44918684f30b0f93e2ef964 /src/backend/utils/adt
parent74c877e8db23df20004f80dd11e383da8cc187a2 (diff)
downloadpostgresql-f318f7fdf85a269ed652e16f67015c3dde960754.tar.gz
postgresql-f318f7fdf85a269ed652e16f67015c3dde960754.zip
Don't run atexit callbacks in quickdie signal handlers.
exit() is not async-signal safe. Even if the libc implementation is, 3rd party libraries might have installed unsafe atexit() callbacks. After receiving SIGQUIT, we really just want to exit as quickly as possible, so we don't really want to run the atexit() callbacks anyway. The original report by Jimmy Yih was a self-deadlock in startup_die(). However, this patch doesn't address that scenario; the signal handling while waiting for the startup packet is more complicated. But at least this alleviates similar problems in the SIGQUIT handlers, like that reported by Asim R P later in the same thread. Backpatch to 9.3 (all supported versions). Discussion: https://www.postgresql.org/message-id/CAOMx_OAuRUHiAuCg2YgicZLzPVv5d9_H4KrL_OFsFP%3DVPekigA%40mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt')
0 files changed, 0 insertions, 0 deletions