Tim Kane <tim.kane@gmail.com> writes:
> I’m migrating a database from 9.2.4 to 9.3.0 and encountering an issue with
> an XML field failing to restore.
Hm, can you restore it into 9.2 either?
AFAICS, pg_dump has absolutely no idea that it should be worried about the
value of xmloption, despite the fact that that setting affects what is
considered valid XML data. What's worse, even if it were attempting to do
something about xmloption, I don't see how it could deal with a case like
this where you have different values inside the same database that require
two different settings in order to parse.
This isn't a 9.3.x bug, it's an aboriginal misdesign of the XML datatype.
Not sure what we can do about it at this point. Perhaps we could invent
a "document_or_content" setting that would tell xml_in to accept either
case? And then have pg_dump force that setting to be used during restore?
regards, tom lane
PS: BTW, I agree with the advice expressed by David J: under no
circumstances put any data you care about on 9.3.0. That release
was rather a disaster from a quality-control standpoint :-(
But that's unrelated to your XML issue.
