From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Dmitry Koval <d.koval@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: Thu, 25 Jan 2024 23:14:55 -0500
Message-ID: <696008.1706242495@sss.pgh.pa.us> (raw)
In-Reply-To: <ZbMJt7HRzxQ6n7j0@paquier.xyz>
References: <5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru>
<1314313.1705259848@sss.pgh.pa.us>
<0eea123f-388a-41ea-9df3-d4606cf9ed8d@postgrespro.ru>
<ZaRvbaQ8V9uGxXGD@paquier.xyz>
<35ef78f9-8958-4225-ae7e-aead71b0feed@postgrespro.ru>
<ZaZI4WAHZ67ZHq7p@paquier.xyz>
<24e7412a-890c-46e3-b17d-addc39ff813f@postgrespro.ru>
<ZacYXgM9A_CSLpD8@paquier.xyz>
<ZbHlgrPLtBZyr_QW@paquier.xyz>
<99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru>
<ZbMJt7HRzxQ6n7j0@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Jan 25, 2024 at 03:12:07PM +0300, Dmitry Koval wrote:
>> I agree that reverting a patch is a good idea if there are concerns about
>> server resources (XML is used by few users and there are even fewer users
>> who need to parse elements larger than 10Mb).
>> For such users it is better to create custom PostgreSQL build.
> And done with f2743a7d70e7.
Related to this: I just read some interesting things in libxml2 2.12's
release notes:
Most of the known issues leading to quadratic behavior in the XML parser
were fixed. Internal hash tables were rewritten to reduce memory
consumption.
A new API function xmlCtxtSetMaxAmplification was added to allow parsing
of files that would otherwise trigger the billion laughs protection.
Could it be that if we see this new function is available and use it,
we could allow more than we have done historically? I don't have a
whole lot of faith here, but perhaps this is worth investigation.
(BTW, 2.12 has created some annoying API breaks, which seems to be why
caiman is failing. We have some work to do there in any case.)
regards, tom lane
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, michael@paquier.xyz, d.koval@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
In-Reply-To: <696008.1706242495@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