Message-ID: <4766CF76.1010105@emolecules.com>
Date: Mon, 17 Dec 2007 11:35:18 -0800
From: Craig James <craig_james@emolecules.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: James Mansion <james@mansionfamily.plus.com>,
	pgsql-performance@postgresql.org
Subject: Multi-threading friendliness (was:  libgcc double-free, backend won't
	die)
References: <200712170852.lBH8qGc18697@momjian.us>
In-Reply-To: <200712170852.lBH8qGc18697@momjian.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:
> James Mansion wrote:
>> I think you have your head in the ground, but its your perogative.
>> *You* might not care, but anyone wanting to use thread-aware libraries
>> (and I'm *not* talking about threading in any Postgres code) will
>> certainly value it if they can do so with some stability.
> 
> I suggest you find out the cause of your problem and then we can do more
> research.  Talking about us changing the Postgres behavior from the
> report of one user who doesn't even have the full details isn't
> productive.

I think you're confusing James Mansion with me (Craig James).  I'm the one with the unresolved problem.

James is suggesting, completely independently of whether or not there's a bug in my system, that a thread-friendly option for Postgres would be very useful.

Don't confuse thread-friendly with a threaded implemetation of Postgres itself.  These are two separate questions.  Thread-friendly involves compile/link options that don't affect the Postgres source code at all.

Craig