Re: libxml incompatibility

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Holger Hoffstaette <holger(at)wizards(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: libxml incompatibility
Date: 2009-03-07 02:44:53
Message-ID: 49B1DFA5.3050905@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Holger Hoffstaette wrote:
> On Fri, 06 Mar 2009 14:32:25 -0600, Kenneth Marshall wrote:
>
>
>> On Fri, Mar 06, 2009 at 02:58:30PM -0500, Andrew Dunstan wrote:
>>
>>> Yes, I discovered this a few weeks ago. It looks like libxml is not
>>> reentrant, so for perl you need to use some other XML library. Very
>>> annoying.
>>>
>>>
>> Ugh! That is worse than a simple library link incompatibility.
>>
>
> http://www.nabble.com/New-libxml-which-is-reentrant---to18329452.html
>
> Seems to me that Perl (?) is calling functions it is not supposed to call
> - I'm guessing due to assumptions about mismatching lifecycles. The
> parsing functions themselves are supposedly reentrant.
>
>
>

Maybe someone can trace the libxml calls ... not sure how exactly ...
given Alvaro's example, it doesn't seem likely to me that this is due to
a call to xmlCleanupParser(), but maybe the perl code invokes by simply
doing "use XML::LibXML;" calls that for some perverse reason.

My interest wasn't so high that I wanted to spend a lot of time on it.
If it didn't work I was just going to move on.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-03-07 03:55:17 Re: libxml incompatibility
Previous Message Andrew Gierth 2009-03-07 02:17:36 NOT NULL constraint vs. composite type (vs. plpgsql)