From: Tom Lane <tgl@sss.pgh.pa.us>
To: d.koval@postgrespro.ru
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18274: Error 'invalid XML content'
In-reply-to: <18274-98d16bc03520665f@postgresql.org>
References: <18274-98d16bc03520665f@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 06 Jan 2024 22:20:36 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1616256.1704651529.1@sss.pgh.pa.us>
Date: Sun, 07 Jan 2024 13:18:49 -0500
Message-ID: <1616257.1704651529@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1616257.1704651529%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The problem is in the libxml2 library (in xmlParseBalancedChunkMemory
> function), which is used in PostgreSQL and does not support the
> XML_PARSE_HUGE flag.
> There have been attempts to correct this problem [1].
> Apparently they were unsuccessful because libxml2 technical support refused
> to fix the xmlParseBalancedChunkMemory function.

> I'd like to know what the community's opinion is regarding this error:
> 1) the error is correct and does not need to be corrected;
> 2) corrections should be made in the libxml2 library;
> 3) corrections should be made in PostgreSQL (maybe need to stop using the
> xmlParseBalancedChunkMemory function or make other corrections);
> 4) ...?

libxml2 seems to be a little moribund, so I'm not sure that waiting
for #2 to happen will yield results.  On the other hand, XML is
pretty much a development backwater in Postgres too, so if you are
hoping for somebody else to do #3 you are unlikely to get anywhere.
If you want to work on #3 yourself, have at it.

			regards, tom lane