From: Dmitry Koval <d.koval@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: Sun, 14 Jan 2024 23:58:07 +0300
Message-ID: <0eea123f-388a-41ea-9df3-d4606cf9ed8d@postgrespro.ru> (raw)
In-Reply-To: <1314313.1705259848@sss.pgh.pa.us>
References: <18274-98d16bc03520665f@postgresql.org>
<1616257.1704651529@sss.pgh.pa.us>
<5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru>
<1314313.1705259848@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: d.koval@postgrespro.ru, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
In-Reply-To: <0eea123f-388a-41ea-9df3-d4606cf9ed8d@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox