From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: Chris <dmagick@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres gets stuck
Date: Thu, 11 May 2006 20:03:26 -0400
Message-ID: <18707.1147392206@sss.pgh.pa.us> (raw)
In-Reply-To: <44635DFE.1060509@modgraph-usa.com>
References: <446135F9.1060608@modgraph-usa.com>
<4461391D.2000800@gmail.com>
<44635DFE.1060509@modgraph-usa.com>
"Craig A. James" <cjames@modgraph-usa.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, cjames@modgraph-usa.com, dmagick@gmail.com
Subject: Re: Postgres gets stuck
In-Reply-To: <18707.1147392206@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox