Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1rP5zD-009GqM-Qs
	for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jan 2024 19:17:36 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1rP5zA-00CUsm-TH
	for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jan 2024 19:17:32 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rP5zA-00CUse-LA
	for pgsql-bugs@lists.postgresql.org; Sun, 14 Jan 2024 19:17:32 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rP5z7-001XAT-RH
	for pgsql-bugs@lists.postgresql.org; Sun, 14 Jan 2024 19:17:31 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 40EJHSQq1314314;
	Sun, 14 Jan 2024 14:17:28 -0500
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'
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>
Comments: In-reply-to Dmitry Koval <d.koval@postgrespro.ru>
	message dated "Sun, 14 Jan 2024 21:28:50 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1314312.1705259848.1@sss.pgh.pa.us>
Date: Sun, 14 Jan 2024 14:17:28 -0500
Message-ID: <1314313.1705259848@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1314313.1705259848%40sss.pgh.pa.us>
Precedence: bulk

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/