Re: libgcc double-free, backend won't die - Mailing list pgsql-performance

From Craig James
Subject Re: libgcc double-free, backend won't die
Date
Msg-id 475EB1B9.3000405@emolecules.com
Whole thread Raw
In response to Re: libgcc double-free, backend won't die  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: libgcc double-free, backend won't die
List pgsql-performance
Alvaro Herrera wrote:
>>> ...Since you've now shown that OpenBabel is
>>> multithreaded, then that's a much more likely cause.
>> Can you elaborate?  Are multithreaded libraries not allowed to be
>> linked to Postgres?
>
> Absolutely not.

Ok, thanks, I'll work on recompiling OpenBabel without thread support.

Since I'm not a Postgres developer, perhaps one of the maintainers could update the Postgres manual.  In chapter
32.9.6,it says, 

  "To be precise, a shared library needs to be created."

This should be amended to say,

  "To be precise, a non-threaded, shared library needs to be created."

Cheers,
Craig



pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: libgcc double-free, backend won't die
Next
From: Craig James
Date:
Subject: Re: libgcc double-free, backend won't die