Defend against null error message reported by libxml2.
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 8 Feb 2019 18:30:42 +0000 (13:30 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 8 Feb 2019 18:31:09 +0000 (13:31 -0500)
commitef922faea703aff4996eab17520cb5201a793701
tree217560fdfbf7a8da9d2237af561d1a218508200d
parent2bcbf687e4265cad739d7fd6cb5f405bae560ed5
Defend against null error message reported by libxml2.

While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others.  Instead of crashing, substitute
"(no message provided)".

I didn't worry about localizing this text, since we aren't
localizing anything else here; besides, if we're on the edge of
OOM, it's unlikely gettext() would work.

Report and fix by Sergio Conde Gómez in bug #15624.

Discussion: https://postgr.es/m/15624-4dea54091a2864e6@postgresql.org
src/backend/utils/adt/xml.c