From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Koval <d.koval@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: Sun, 14 Jan 2024 14:17:28 -0500
Message-ID: <1314313.1705259848@sss.pgh.pa.us> (raw)
In-Reply-To: <5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru>
References: <18274-98d16bc03520665f@postgresql.org>
<1616257.1704651529@sss.pgh.pa.us>
<5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru>
Dmitry Koval <d.koval@postgrespro.ru> writes:
> Attached a patch that adds the use of XML_PARSE_HUGE flag for libxml2
> functions and replaces some functions (that do not support this flag)
> with their equivalents.
Thanks for doing this work! Please add an entry to the upcoming
commitfest[1] to ensure we don't forget about it.
> Maybe it would be a good idea to add a GUC-variable for using of the
> XML_PARSE_HUGE flag?
That strikes me as a completely awful idea. Is there some downside
to XML_PARSE_HUGE?
regards, tom lane
[1] https://commitfest.postgresql.org/47/
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: tgl@sss.pgh.pa.us, d.koval@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
In-Reply-To: <1314313.1705259848@sss.pgh.pa.us>
* 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