Excerpts from Robert Haas's message of lun jul 25 11:20:55 -0400 2011:
> On Sun, Jul 24, 2011 at 5:06 PM, noordsij <noordsij@cs.helsinki.fi> wrote:
> >> Any idea what query triggered this?
> >
> > Only up to which stored procedure (which itself contains multiple
> > statements).
>
> If you provide a reproducible test case, we can probably get this fixed.
>
> Otherwise, we probably can't.
But why is libxml calling pthread_mutex_lock and such? Unless libxml is
making itself multithread inside a backend, that shouldn't matter --
much less cause a crash.
Note (to the OP) that it's totally unexpected to have a Postgres backend
become multithreaded, and has been shown to be dangerous when a library
made it so.
--
Ãlvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support