Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id CF1132E0132 for ; Sun, 16 Dec 2007 14:16:30 -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 00355-07 for ; Sun, 16 Dec 2007 14:16:27 -0400 (AST) Received: from oxford.xeocode.com (unknown [87.127.95.196]) by postgresql.org (Postfix) with ESMTP id EA4702E0120 for ; Sun, 16 Dec 2007 14:16:26 -0400 (AST) Received: from localhost ([127.0.0.1] helo=oxford.xeocode.com) by oxford.xeocode.com with esmtp (Exim 4.67) (envelope-from ) id 1J3y2H-0000hZ-MN; Sun, 16 Dec 2007 18:16:21 +0000 To: "Tom Lane" Cc: "James Mansion" , "Magnus Hagander" , "Craig James" , "Alvaro Herrera" , Subject: Re: libgcc double-free, backend won't die In-Reply-To: <27316.1197828101@sss.pgh.pa.us> (Tom Lane's message of "Sun\, 16 Dec 2007 13\:01\:41 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-Draft-From: ("nnimap+mail01.enterprisedb.com:INBOX" 54576) 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> <20071211155703.GT31937@svr2.hagander.net> <87r6htw4e7.fsf@oxford.xeocode.com> <476564D6.7090702@mansionfamily.plus.com> <27316.1197828101@sss.pgh.pa.us> From: Gregory Stark Organization: EnterpriseDB Date: Sun, 16 Dec 2007 18:16:18 +0000 Message-ID: <877ijeqzd9.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/243 X-Sequence-Number: 28059 "Tom Lane" writes: > James Mansion writes: >> Is there any particular reason not to ensure that any low-level >> threading support in libc is enabled right >> from the get-go, as a build-time option? > > Yes. > 1) It's of no value to us > 2) On many platforms there is a nonzero performance penalty And the only reason to do that would be to work around one bug in one small range of glibc versions. If you're going to use a multi-threaded library (which isn't very common since it's hard to do safely for all those other reasons) surely using a version of your OS without any thread related bugs is a better idea. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support!