| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18274: Error 'invalid XML content' |
| Date: | 2024-01-14 20:58:07 |
| Message-ID: | 0eea123f-388a-41ea-9df3-d4606cf9ed8d@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks!
> Thanks for doing this work! Please add an entry to the upcoming
> commitfest[1] to ensure we don't forget about it.
Added.
> Is there some downside to XML_PARSE_HUGE?
I didn't see any problems during simple testing of patch with the
XML_PARSE_HUGE.
Extended testing will be performed soon.
Then (I hope) we will send a trial version of PostgreSQL with a patch to
customers who use XML.
--
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-01-14 23:34:05 | Re: BUG #18274: Error 'invalid XML content' |
| Previous Message | Tom Lane | 2024-01-14 19:17:28 | Re: BUG #18274: Error 'invalid XML content' |