pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Dmitry Koval <d.koval@postgrespro.ru>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: Thu, 25 Jan 2024 15:12:07 +0300
Message-ID: <99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru> (raw)
In-Reply-To: <ZbHlgrPLtBZyr_QW@paquier.xyz>
References: <18274-98d16bc03520665f@postgresql.org>
	<1616257.1704651529@sss.pgh.pa.us>
	<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>

> he security team has discussed 2197d06224a1 after a report from
> coverity regarding the effects that issues like [1] would create in
> the backend, and concluded that this patch should be reverted because
> this could cause the backend to waste plently of CPU and/or memory
> even if the application applied checks on the size of the data given
> in input, and libxml2 does not offer guarantees that input limits are
> respected under XML_PARSE_HUGE.

Thanks for info!

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.

-- 
With best regards,
Dmitry Koval

Postgres Professional: http://postgrespro.com

view thread (16+ messages)  latest in thread

Message-ID: <99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru>
Permalink:  ../99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru/
Also on:    postgresql.org/message-id/99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru

copy link · copy postgr.es

reply

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, michael@paquier.xyz, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18274: Error 'invalid XML content'
  In-Reply-To: <99aae616-db97-4632-8934-4f39e7105631@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