Re: PG versus libxml2 2.12.x
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-01-29T15:59:06Z
Lists: pgsql-hackers
Attachments
- v2-cope-with-libxml2-API-changes.patch (text/x-diff) patch v2
I wrote: > Peter Eisentraut <peter@eisentraut.org> writes: >> In PL/Tcl, we used to have these CONST84 and CONST86 things, for similar >> reasons. Maybe that would be another approach. > Yeah, if the simple cast approach turns out to create warnings, > we'll have to fall back on using actually different declarations. > I'm hoping to not have to go there. Actually ... what I really want to avoid is adding a configure test. The alternative to that would be an #if test on LIBXML_VERSION, which I'd initially not wanted to do ... but I now notice that we already have one of those for a nearby purpose (coping with a different change in libxml2's error APIs). So adding another one of those doesn't seem so bad after all. I now like the attached approach better. regards, tom lane
Commits
-
Fix incompatibilities with libxml2 >= 2.12.0.
- 400928b83bd2 17.0 landed
- b2fd1dab9024 12.18 landed
- 7c53b1977ba6 13.14 landed
- 29e25a6b1eb1 14.11 landed
- e02fea093ebb 16.2 landed
- 3f8ac13b1976 15.6 landed