Re: Regression with large XML data input

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Erik Wienhold <ewie(at)ewie(dot)name>, zengman <zengman(at)halodbtech(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Regression with large XML data input
Date: 2025-12-29 00:24:29
Message-ID: aVHKPeYX3csE1Jwg@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 25, 2025 at 12:50:38PM -0500, Tom Lane wrote:
> That would be my preferred answer, but after a quick census of the
> buildfarm I'm not sure we can get away with it. The animals that
> are showing these warnings are all running RHEL 10 or clones of it,
> which is going to be in-support till 2035 or so. Maybe Red Hat
> will upgrade to a newer libxml2 version than whatever they chose
> for RHEL 10.0, but I would not count on it.

Hmm. Having to deal with these warnings until 2035 kind of sucks. Do
you think that it be worth forcing the use of
-Wno-deprecated-declarations only for versions older than 2.13.3 in
the Makefiles where we could see these warnings?

As a whole, this kind of enforcement gives me mixed feelings, because
it would also mean that we would miss what looks like legit
deprecation warnings that we had better look at and study, even for
LLVM. At least not enforcing any policy lets us know about these
issues.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-12-29 00:39:38 Re: Fixing some ancient errors in hash join costing
Previous Message Michael Paquier 2025-12-29 00:14:31 Re: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs