Re: libgcc double-free, backend won't die

From: Craig James <craig_james(at)emolecules(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: libgcc double-free, backend won't die
Date: 2007-12-11 15:50:17
Message-ID: 475EB1B9.3000405@emolecules.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Craig James 2007-12-11 15:53:15 Re: libgcc double-free, backend won't die
Previous Message Tom Lane 2007-12-11 15:43:06 Re: libgcc double-free, backend won't die