Hi all,
I have this problem today: one thread of our application hung, and
we found the thread waiting for the result of poll() function. poll()
was called by pgSocketCheck(). So is it a bug of pg? I found the bug
report from website(http://archives.postgresql.org/pgsql-bugs/2008-02/msg00260.php),
and want to know:
1. Has this problem been solved in the newest version?
2. If not, what shall I do to avoid this problem?
Thanks a lot!
PS: version info:
PostgreSQL version: PostgreSQL 8.3.3 on i686-pc-linux-gnu
Operating system: CentOS release 5.2 (Final)
Kernel version: Linux version 2.6.18-92.el5xen
(mockbuild@builder16.centos.org)
gdb info:
(gdb) bt
#0 0x00d31402 in __kernel_vsyscall ()
#1 0x003d3dc3 in poll () from /lib/i686/nosegneg/libc.so.6
#2 0x0013de5d in pqSocketCheck () from /usr/local/pgsql/lib/libpq.so.5
#3 0x0013df8d in pqWaitTimed () from /usr/local/pgsql/lib/libpq.so.5
#4 0x0013e003 in pqWait () from /usr/local/pgsql/lib/libpq.so.5
#5 0x0013d792 in PQgetResult () from /usr/local/pgsql/lib/libpq.so.5
--
Yours Sincerely,
Liz