On Wed, Apr 11, 2012 at 2:04 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> rnysmile@yahoo.com writes:
>> This month, we upgrade the libpq5 from =A08.4.7 to 8.4.11.(libpq-dev
>> 8.4.11-0ubuntu0.11.04) Our service program become unstable after upgradi=
ng.
>
> It seems rather improbable that a deadlock inside glibc would be our
> bug. =A0Also, I've just looked very carefully through all the diffs
> between 8.4.7 and 8.4.11 (or at least, all the diffs affecting libpq)
> and I don't see anything that could plausibly lead to this behavior.
Is it's possible it's this? It's fixed in a version of libc that
post-dates Ubuntu 11.0.4 as far as I can tell.
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/838975
Otherwise, just as a comment, in my experience pthread problems often
are triggered by generic memory handling bugs like buffer overruns or
writing to freed or realloced blocks. These kinds of bugs can corrupt
any dynamically managed memory block and typically pthreads includes
such memory blocks internally.
--=20
greg