| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Holger Hoffstaette <holger(at)wizards(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: libxml incompatibility |
| Date: | 2009-03-07 03:55:17 |
| Message-ID: | 20090307035517.GN3901@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> Holger Hoffstaette wrote:
>
>> 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.
Something that came to my mind was that maybe the change of memory
management (to make it use palloc) could be confusing libxml somehow.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-03-07 04:11:10 | Re: libxml incompatibility |
| Previous Message | Andrew Dunstan | 2009-03-07 02:44:53 | Re: libxml incompatibility |