Re: BUG #5079: postgres killed by signal 11 when executing xslt_process function from xml2 contrib module.

"dolejsi jiri" <dolejsi@mail.ctk.cz> writes:
> executing following query 2 times crashes postgres server:

The stack trace is

#0  0x0000003d7e42e989 in xmlCleanupCharEncodingHandlers ()
   from /usr/lib64/libxml2.so.2
#1  0x0000003d7e437725 in xmlCleanupParser () from /usr/lib64/libxml2.so.2
#2  0x00007fac004e270d in xslt_process (fcinfo=0x7fff59701da0)
    at xslt_proc.c:124
#3  0x0000000000566154 in ExecMakeFunctionResult (
    fcache=<value optimized out>, econtext=<value optimized out>,
    isNull=0x7fff5970222f "", isDone=0x0) at execQual.c:1686
#4  0x000000000056141c in ExecEvalExprSwitchContext (expression=0x7,
    econtext=0x0, isNull=0x1c258a0 '\177' <repeats 200 times>...,
    isDone=0x1c25870) at execQual.c:4030

which is probably sufficient evidence that this is another variant
of the known memory management issues with contrib/xml2:
http://archives.postgresql.org/message-id/4A6A276A.6090405@dunslane.net

So far no one has mustered the interest/energy to fix it.

            regards, tom lane