| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stefan Fercot <stefan(dot)fercot(at)dalibo(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question about xmloption and pg_restore |
| Date: | 2018-05-18 19:50:02 |
| Message-ID: | CA+TgmoYgMwkp-t=ndrf+hf2h7jOe_hJdpzFUPokTLeFbV215vA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 17, 2018 at 9:37 AM, Stefan Fercot <stefan(dot)fercot(at)dalibo(dot)com> wrote:
> When restoring a plain SQL dump, we got the message :
>
> ERROR: invalid XML content
> DETAIL: line 1: StartTag: invalid element name
> <!DOCTYPE qgis PUBLIC 'http://mrcc.com/qgis.dtd' 'SYSTEM'>
> ^
> CONTEXT: COPY layer_styles, line 1, column styleqml: "<!DOCTYPE qgis PUBLIC
> 'http://mrcc.com/qgis.dtd' 'SYSTEM'>
>
> Adding "SET XML OPTION DOCUMENT;" in top of the dump file allows to restore
> it.
Hmm. I thought that xmloption = 'content' was supposed to be strictly
more permissive than xmloption = 'document'.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-18 19:54:39 | Re: 'tuple concurrently updated' error w/o visible catalog updates |
| Previous Message | Robert Haas | 2018-05-18 19:47:42 | Re: Removing unneeded self joins |