Received: from localhost (unknown [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 211352E2EE3
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 11 Dec 2007 11:57:08 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024)
	with ESMTP id 68176-08 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 11 Dec 2007 11:57:04 -0400 (AST)
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by postgresql.org (Postfix) with ESMTP id 3E9202E2ED6
	for <pgsql-performance@postgresql.org>;
	Tue, 11 Dec 2007 11:57:05 -0400 (AST)
Received: by svr2.hagander.net (Postfix, from userid 1000)
	id ABD0EDCC540; Tue, 11 Dec 2007 16:57:03 +0100 (CET)
Date: Tue, 11 Dec 2007 16:57:03 +0100
From: Magnus Hagander <magnus@hagander.net>
To: Craig James <craig_james@emolecules.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-performance@postgresql.org
Subject: Re: libgcc double-free, backend won't die
Message-ID: <20071211155703.GT31937@svr2.hagander.net>
References: <4729B1E9.2080306@gmail.com> <475E4133.5080009@emolecules.com>
	<20071211112128.GB4708@alvh.no-ip.org>
	<475EA754.1090307@emolecules.com>
	<20071211151416.GD10710@alvh.no-ip.org>
	<475EA9FD.9000706@emolecules.com>
	<20071211152010.GE10710@alvh.no-ip.org> <475EAB69.9@emolecules.com>
	<20071211152838.GH4708@alvh.no-ip.org>
	<475EB1B9.3000405@emolecules.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <475EB1B9.3000405@emolecules.com>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200712/142
X-Sequence-Number: 27958

On Tue, Dec 11, 2007 at 07:50:17AM -0800, Craig James wrote:
> 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."
> 

Just before someone goes ahead and writes it (which is probably a good idea
in general), don't write it just like taht - because it's platform
dependent. On win32, you can certainly stick a threaded library to it -
which is good, because most (if not all) win32 libs are threaded... Now, if
they actually *use* threads explicitly things might break (but most likely
not from that specifically), but you can link with them without the
problem. I'm sure there are other platforms with similar situations.


//Magnus