Andrew Dunstan <andrew@dunslane.net> writes:
> First, I propose that we abandon this mangling, if, and only if, the xml
> is in fact a well formed XML document. Since the whole point of the
> mangling is to handle situations where the XML is not a well formed
> document, that seems fairly straight-forward. If this change were to
> upset any user, it must be because they are relying on undisputably
> incorrect results.
> Second, I propose that, in the remaining cases, where we do mangle the
> XML, if the xpath expression does not begin with a '/', instead of
> prepending it with '/x/, which can not possibly be correct under any
> circumstance, we prepend it with '/x//' which has some possibility of
> giving correct results.
Hmm, does this proposal require adding a test of well-formed-ness to
a code path that doesn't currently have one? If so, is that likely
to contribute any noticeable slowdown?
I can't offhand see an objection to this other than possible performance
impact.
regards, tom lane
