aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/shippable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-30 10:52:20 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-30 10:52:20 -0400
commite45b0dfa1f1028948decad3abd3b0f6e913a44b0 (patch)
treecb8dc2fd07d362f1e58a2eb969ec0f6723c72eb9 /contrib/postgres_fdw/shippable.c
parent3465c8a8692fb628bc2710fbeedb9aeb534b0400 (diff)
downloadpostgresql-e45b0dfa1f1028948decad3abd3b0f6e913a44b0.tar.gz
postgresql-e45b0dfa1f1028948decad3abd3b0f6e913a44b0.zip
Fix portability fallout from commit dc227eb82.
Give up on trying to mechanically forbid abort() within libpq. Even though there are no such calls in the source code, we've now seen three different scenarios where build toolchains silently insert such calls: gcc does it for profiling, some platforms implement assert() using it, and icc does so for no visible reason. Checking for accidental use of exit() seems considerably more important than checking for abort(), so we'll settle for doing that for now. Also, filter out __cxa_atexit() to avoid a false match. It seems that OpenBSD inserts a call to that despite the fact that libpq contains no C++ code. Discussion: https://postgr.es/m/3128896.1624742969@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/shippable.c')
0 files changed, 0 insertions, 0 deletions