aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
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:30 +0300
commit2332020d6d1912bff4c03a8c2b37ad1c8b184281 (patch)
treeb40e47542a55953bd2529bfd80af6233272aca99 /src/backend/executor/nodeModifyTable.c
parent9446d7157740a09613175209c9e4eef02d3d92db (diff)
downloadpostgresql-2332020d6d1912bff4c03a8c2b37ad1c8b184281.tar.gz
postgresql-2332020d6d1912bff4c03a8c2b37ad1c8b184281.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/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions