diff options
author | Michael Paquier | 2025-07-06 23:53:57 +0000 |
---|---|---|
committer | Michael Paquier | 2025-07-06 23:53:57 +0000 |
commit | 8aa54aa7eefbf738999ae855d9192bc57756201e (patch) | |
tree | b01c08314b7aa348eb64c86071c4a3b5f5793c38 | |
parent | 21c9756db6458f859e6579a6754c78154321cb39 (diff) |
Fix incompatibility with libxml2 >= 2.14
libxml2 has deprecated the members of xmlBuffer, and it is recommended
to access them with dedicated routines. We have only one case in the
tree where this shows an impact: xml2/xpath.c where "content" was
getting directly accessed. The rest of the code looked fine, checking
the PostgreSQL code with libxml2 close to the top of its "2.14" branch.
xmlBufferContent() exists since year 2000 based on a check of the
upstream libxml2 tree, so let's switch to it.
Like 400928b83bd2, backpatch all the way down as this can have an impact
on all the branches already released once newer versions of libxml2 get
more popular.
Reported-by: Walid Ibrahim <[email protected]>
Reviewed-by: Tom Lane <[email protected]>
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 13
-rw-r--r-- | contrib/xml2/xpath.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/xml2/xpath.c b/contrib/xml2/xpath.c index 3f733405ec6..11216b9b7f9 100644 --- a/contrib/xml2/xpath.c +++ b/contrib/xml2/xpath.c @@ -209,7 +209,7 @@ pgxmlNodeSetToText(xmlNodeSetPtr nodeset, xmlBufferWriteChar(buf, ">"); } - result = xmlStrdup(buf->content); + result = xmlStrdup(xmlBufferContent(buf)); if (result == NULL || pg_xml_error_occurred(xmlerrcxt)) xml_ereport(xmlerrcxt, ERROR, ERRCODE_OUT_OF_MEMORY, "could not allocate result"); |