Re: Deprecation warnings on Rocky 10.2 with current dev branch - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Deprecation warnings on Rocky 10.2 with current dev branch
Date
Msg-id 5c76c136-73df-4112-a583-7d652c387080@dunslane.net
Whole thread
In response to Re: Deprecation warnings on Rocky 10.2 with current dev branch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Deprecation warnings on Rocky 10.2 with current dev branch
List pgsql-hackers
On 2026-07-17 Fr 10:38 AM, Tom Lane wrote:
> "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com> writes:
>> I've just noticed this while building from the dev branch on Rocky 10.2 x64:
>> ../postgresql/src/backend/utils/adt/xml.c:1961:17: warning: ‘xmlKeepBlanksDefault’ is deprecated
[-Wdeprecated-declarations]
>>   1961 |                 xmlKeepBlanksDefault(save_keep_blanks);
>>        |                 ^~~~~~~~~~~~~~~~~~~~
>> Is this known already?
> Yeah.  It's annoying as heck, because they deprecated that without
> providing an adequate replacement.  The replacement is claimed to
> be "Use the modern options API with XML_PARSE_NOBLANKS", but there
> is no direct equivalent to xmlParseBalancedChunkMemory that takes
> an options argument.
>
> So to get rid of this, we're looking at a probably-nontrivial
> rewrite of xml_parse(), with possibly some user-visible behavioral
> changes, and who-knows-what effects for compatibility across
> different libxml2 versions.
>
> If you feel like researching that, have at it.
>

I think we can probably use xmlParseInNodeContext(), which does take an 
options argument. Did you look at that?


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Paul Kim
Date:
Subject: Restore vacuum_delay_point() in GIN posting-tree leaf vacuum
Next
From: Tom Lane
Date:
Subject: Re: Deprecation warnings on Rocky 10.2 with current dev branch