X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 3A24F9FB1A5 for ; Thu, 11 May 2006 21:03:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09438-06 for ; Thu, 11 May 2006 21:03:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 215509FADD1 for ; Thu, 11 May 2006 21:03:35 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4C03QnG018708; Thu, 11 May 2006 20:03:27 -0400 (EDT) To: "Craig A. James" cc: Chris , pgsql-performance@postgresql.org Subject: Re: Postgres gets stuck In-reply-to: <44635DFE.1060509@modgraph-usa.com> References: <446135F9.1060608@modgraph-usa.com> <4461391D.2000800@gmail.com> <44635DFE.1060509@modgraph-usa.com> Comments: In-reply-to "Craig A. James" message dated "Thu, 11 May 2006 08:53:34 -0700" Date: Thu, 11 May 2006 20:03:26 -0400 Message-ID: <18707.1147392206@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/320 X-Sequence-Number: 19107 "Craig A. James" writes: > My suspicion is that it's an incompatibility between malloc() > libraries. On Linux there's only supposed to be one malloc, ie, glibc's version. On other platforms I'd be worried about threaded vs non-threaded libc (because the backend is not threaded), but not Linux. There may be a more basic threading problem here, though, rooted in the precise fact that the backend isn't threaded. If you're trying to use any libraries that assume they can have multiple threads, I wouldn't be at all surprised to see things go boom. C++ exception handling could be problematic too. Or it could be a garden variety glibc bug. How up-to-date is your platform? regards, tom lane