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 1ugDQ6-00HQwx-Rx for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jul 2025 02:16:55 +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 1ugDQ5-003SZL-Sf for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jul 2025 02:16:54 +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 ) id 1ugDQ5-003SZC-GM for pgsql-hackers@lists.postgresql.org; Mon, 28 Jul 2025 02:16:53 +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.96) (envelope-from ) id 1ugDQ3-0018C6-2w for pgsql-hackers@lists.postgresql.org; Mon, 28 Jul 2025 02:16:52 +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 56S2GlDS314266; Sun, 27 Jul 2025 22:16:47 -0400 From: Tom Lane To: Michael Paquier cc: Robert Treat , Jim Jones , Postgres hackers , Erik Wienhold Subject: Re: Regression with large XML data input In-reply-to: References: <1569825.1753327718@sss.pgh.pa.us> <1685956.1753380629@sss.pgh.pa.us> <1691195.1753383449@sss.pgh.pa.us> <1721385.1753385039@sss.pgh.pa.us> <7a9a9804-01d8-4489-a831-1a222bae6705@uni-muenster.de> <1944118.1753467686@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Mon, 28 Jul 2025 11:09:33 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <314264.1753669007.1@sss.pgh.pa.us> Date: Sun, 27 Jul 2025 22:16:47 -0400 Message-ID: <314265.1753669007@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Fri, Jul 25, 2025 at 02:21:26PM -0400, Tom Lane wrote: >> However, from Jim Jones' result upthread, a "minor update" of libxml2 >> could also have caused this problem: 2.9.7 and 2.9.14 behave >> differently. So we don't have sole control --- or sole responsibility >> --- here. > This sentence is incorrect after I have double-checked the behaviors I > am seeing based on local builds of libxml2 2.9.7 and 2.9.14. Hmm, okay, I misread Jim's results then. But there still remains the big question: what reason is there to believe that it's safe to return to the old behavior? If newer libxml2 versions report XML_ERR_RESOURCE_LIMIT on the same input, doesn't it seem likely that there's a live hazard in the old code? regards, tom lane