>
>
> From: Tom Lane
>
> 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
Tim Kane 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 se
Hi all,
I’m migrating a database from 9.2.4 to 9.3.0 and encountering an issue with an
XML field failing to restore.
I’m using pg_dump 9.3.0 as follows (with 9.2.4 on 5433 and 9.3.0 on 5432). I
have verified my paths, it’s definitely using the 9.3.0 binaries. Both source
and target are using
Tim Kane wrote
> I suspect this might be resolved in a newer point release of 9.3, however
> I
> don’t have the luxury on this particular host right now.
>
> Any suggestions how I might convince 9.3.0 to accept the dump from 9.2.4?
Given the history of 9.3 if you cannot use the most current point
Hi all,
I’m migrating a database from 9.2.4 to 9.3.0 and encountering an issue with
an XML field failing to restore.
I’m using pg_dump 9.3.0 as follows (with 9.2.4 on 5433 and 9.3.0 on 5432).
I have verified my paths, it’s definitely using the 9.3.0 binaries. Both
source and target are using UTF8
