aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-12-16 10:58:49 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-12-16 11:10:40 -0500
commit37bef842f5530fc9f4a48daba9f4709ee5e36c9b (patch)
tree07537c49f5b6b0191a5f56537a69d1cc9e3382a9 /contrib/postgres_fdw/postgres_fdw.c
parente52f8b301ed54aac5162b185b43f5f1e44b6b17e (diff)
downloadpostgresql-37bef842f5530fc9f4a48daba9f4709ee5e36c9b.tar.gz
postgresql-37bef842f5530fc9f4a48daba9f4709ee5e36c9b.zip
Convert xml_in to report errors softly.
The key idea here is that xml_parse must distinguish hard errors from soft errors. We want to throw a hard error for libxml initialization failures: those might be out-of-memory, or something else, but in any case they are not the fault of the input string. If we get to the point of parsing the input, and something goes wrong, we can fairly consider that to mean bad input. One thing that arguably does mean bad input, but I didn't trouble to handle softly, is encoding conversion failure while converting the server encoding to UTF8. This might be something to improve later, but it seems like a pretty low-probability scenario. Discussion: https://postgr.es/m/3564577.1671142683@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions