| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XML Issue with DTDs |
| Date: | 2013-12-23 02:45:02 |
| Message-ID: | CA+TgmoZNHVhco-kQPvQRvCv+s9SR5sYkzmexO5aAMKkLBsUfqg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 20, 2013 at 8:16 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
> On Dec20, 2013, at 18:52 , Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Thu, Dec 19, 2013 at 6:40 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
>>> Solving this seems a bit messy, unfortunately. First, I think we need to have some XMLOPTION value which is a superset of all the others - otherwise, dump & restore won't work reliably. That means either allowing DTDs if XMLOPTION is CONTENT, or inventing a third XMLOPTION, say ANY.
>>
>> Or we can just decide that it was a bug that this was ever allowed,
>> and if you upgrade to $FIXEDVERSION you'll need to sanitize your data.
>> This is roughly what we did with encoding checks.
>
> What exactly do you suggest we outlaw?
<!DOCTYPE> anywhere but at the beginning.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-12-23 04:30:56 | Re: Issue with PGC_BACKEND parameters |
| Previous Message | Robert Haas | 2013-12-23 02:43:57 | Re: [PATCH] Make various variables read-only (const) |