From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | andreagrassi(at)sogeasoft(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6342: libpq blocks forever in "poll" function |
Date: | 2011-12-16 08:23:34 |
Message-ID: | 4EEB0006.7080205@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 12/16/2011 03:45 PM, andreagrassi(at)sogeasoft(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6342
> Logged by: Andrea Grassi
> Email address: andreagrassi(at)sogeasoft(dot)com
> PostgreSQL version: 8.4.8
> Operating system: SUSE SLES 10 SP4 64 BIT
> Description:
>
> Hi,
> I have a big and strange problem. Sometimes, libpq remains blocked in “poll”
> function even if the server has already answered to the query. If I attach
> to the process using kdbg I found this stack:
>
> __kernel_vsyscall()
> poll() from /lib/libc.so.6
Given all you described (thanks for all the detail!) then if client and
server are on different hosts this could easily be a NIC driver or HW
issue. It'd be interesting to see the output of:
ps -C testprogramname -o wchan:80=
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-12-16 08:24:36 | Re: BUG #6342: libpq blocks forever in "poll" function |
Previous Message | andreagrassi | 2011-12-16 07:45:42 | BUG #6342: libpq blocks forever in "poll" function |