libxml incompatibility - Mailing list pgsql-hackers

From Alvaro Herrera
Subject libxml incompatibility
Date
Msg-id 20090306191404.GK3901@alvh.no-ip.org
Whole thread Raw
Responses Re: libxml incompatibility  (Kenneth Marshall <ktm@rice.edu>)
Re: libxml incompatibility  (Andrew Dunstan <andrew@dunslane.net>)
Re: libxml incompatibility  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

It seems that if you load libxml into a backend for whatever reason (say
you create a table with a column of type xml) and then create a plperlu
function that "use XML::LibXML", we get a segmentation fault.

This sequence reproduces the problem for me in 8.3:

create table xmlcrash (a xml);
insert into xmlcrash values ('<a />');
create function xmlcrash() returns void language plperlu as $$ use XML::LibXML; $$;

The problem is reported as

TRAP: BadArgument(«!(((context) != ((void *)0) && (((((Node*)((context)))->type) == T_AllocSetContext))))», Archivo:
«/pgsql/source/83_rel/src/backend/utils/mmgr/mcxt.c»,Línea: 507)
 


-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposed Patch to Improve Performance of Multi-BatchHash Join for Skewed Data Sets
Next
From: Robert Haas
Date:
Subject: Re: Proposed Patch to Improve Performance of Multi-BatchHash Join for Skewed Data Sets