> I also have a client suffering an occasional 'application hang' running Suse 11.2 and postgressql 8.4
> on an 8 core box which is not reproducable in a VMWare test environment.
> Access to postgres is libpq 127.0.0.1 as well.
> Unfortunately the client must restart ASAP and I have not produced a 'test case'.
But you examined the stack ? It's similar to mine ?
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xf76539cb in poll () from /lib/libc.so..
#2 0xf770d39a in pqSocketCheck () from /home/pg/pgsql/lib-32/libpq.so.5
#3 0xf770d49d in pqWaitTimed () from /home/pg/pgsql/lib-32/libpq.so.5
#4 0xf770d513 in pqWait () from /home/pg/pgsql/lib-32/libpq.so.5
#5 0xf770c6d6 in PQgetResult () from /home/pg/pgsql/lib-32/libpq.so.5
#6 0xf770c89c in PQexecFinish () from /home/pg/pgsql/lib-32/libpq.so.5
Can you specify the details of hardware and platform of your machine to understand if it can have something in common with the mine and so to understand the reason/origin of the bug?
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2011-12-20 16:38:23|
|Subject: Re: R: R: R: BUG #6342: libpq blocks forever in "poll" function |
|Previous:||From: Andrea Grassi||Date: 2011-12-20 16:15:43|
|Subject: R: R: R: BUG #6342: libpq blocks forever in "poll" function|