aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-06-28 14:17:42 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-06-28 14:17:42 -0400
commit1603deca34ef403fc40d471ba6512d9f170ba7b5 (patch)
tree733e39099cab7880c35f69cd5c2af7c5f9bdeb1b /contrib/postgres_fdw/postgres_fdw.c
parentbe567deb3ac952e41edc81b8c08a0dc6115c5f62 (diff)
downloadpostgresql-1603deca34ef403fc40d471ba6512d9f170ba7b5.tar.gz
postgresql-1603deca34ef403fc40d471ba6512d9f170ba7b5.zip
Don't use abort(3) in libpq's fe-print.c.
Causing a core dump on out-of-memory seems pretty unfriendly, and surely is far outside the expected behavior of a general-purpose library. Just print an error message (as we did already) and return. These functions unfortunately don't have an error return convention, but code using them is probably just looking for a quick-n-dirty print method and wouldn't bother to check anyway. Although these functions are semi-deprecated, it still seems appropriate to back-patch this. In passing, also back-patch b90e6cef1, just to reduce cosmetic differences between the branches. Discussion: https://postgr.es/m/3122443.1624735363@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions