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 ) id 1rP7Ye-009Q9v-69 for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jan 2024 20:58:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rP7Yc-00CbjN-4X for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jan 2024 20:58:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rP7Yb-00CbjF-No for pgsql-bugs@lists.postgresql.org; Sun, 14 Jan 2024 20:58:13 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rP7YX-001m7R-9b for pgsql-bugs@lists.postgresql.org; Sun, 14 Jan 2024 20:58:12 +0000 Received: from [192.168.1.120] (unknown [46.164.243.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: d.koval@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 7D0B2E2103C; Sun, 14 Jan 2024 23:58:07 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1705265887; bh=Wnd+V5sAiarfhwWdq45nJJfZki/kK6nO8q5Yl1Vlfss=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=io39mpBMOI5CIEn0Q0lXE4yr4gGaKSe3bKmFzIVxsE1DFSo7ixKvzt7tfSIIbGfcH xGSRreL/OD1Sm3nLOVHqTZdbdAkHz5penorMnQM+2i1YJG2qaFYhmo2rTtJm6SleoS pmFpbjiHaQc4+IAsUdkCpIIh68akYzU8isiktyaB800aX8vZ0qMfCMdrFXpKgQdp53 mcPW4D8YVZKomoNAa1wY1Adq2K80hds102+mybADcfS58LUs18Td7JI1+2HjUc+Kp5 Q8kDmKUjmr8CU2piYv9QCxeJs7nlU9KV/acWUZTq+/iQash/JnjKF/ehnGdEv2idpo 3MnGBq6uw2B2w== Message-ID: <0eea123f-388a-41ea-9df3-d4606cf9ed8d@postgrespro.ru> Date: Sun, 14 Jan 2024 23:58:07 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18274: Error 'invalid XML content' Content-Language: en-US To: Tom Lane Cc: pgsql-bugs@lists.postgresql.org References: <18274-98d16bc03520665f@postgresql.org> <1616257.1704651529@sss.pgh.pa.us> <5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru> <1314313.1705259848@sss.pgh.pa.us> From: Dmitry Koval In-Reply-To: <1314313.1705259848@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thanks! > Thanks for doing this work! Please add an entry to the upcoming > commitfest[1] to ensure we don't forget about it. Added. > Is there some downside to XML_PARSE_HUGE? I didn't see any problems during simple testing of patch with the XML_PARSE_HUGE. Extended testing will be performed soon. Then (I hope) we will send a trial version of PostgreSQL with a patch to customers who use XML. -- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com