Comment 13 for bug 322887

After looking more closely at the threads using gdb, it seems that most of them are not really blocked while waiting to acquire a lock but they are actually blocked on a call to psycopg2. One potential solution was to try upgrading to the latest version of the library but, after building and installing, the same problem occured. Unfortunately, this doesn't leave much to go on considering that the Storm code only really uses psycopg2 to obtain a raw connection.

(gdb) thread 2
(gdb) where
#0 0xb7f1c410 in __kernel_vsyscall ()
#1 0xb7e43c07 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5d5910a in ?? () from /usr/lib/libpq.so.5
#3 0xb5d59246 in ?? () from /usr/lib/libpq.so.5
#4 0xb5d592c3 in ?? () from /usr/lib/libpq.so.5
#5 0xb5d58972 in PQgetResult () from /usr/lib/libpq.so.5
#6 0xb5d58a8c in ?? () from /usr/lib/libpq.so.5
#7 0xb5d7f9b2 in ?? () from /usr/lib/python2.5/site-packages/psycopg2/_psycopg.so
#8 0xb5d85cdc in ?? () from /usr/lib/python2.5/site-packages/psycopg2/_psycopg.so
#9 0xb5d86463 in ?? () from /usr/lib/python2.5/site-packages/psycopg2/_psycopg.so
#10 0x0805cb97 in PyObject_Call (func=0x1, arg=0xba3c8ac, kw=0xba2968c) at ../Objects/abstract.c:1861
#11 0x080c7e04 in PyEval_EvalFrameEx (f=0xa0d500c, throwflag=0) at ../Python/ceval.c:3853
#12 0x080cb1f7 in PyEval_EvalCodeEx (co=0x8df2020, globals=0x8df03e4, locals=0x0, args=0xbc2e2b8, argcount=4, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0)
    at ../Python/ceval.c:2836
...