On Wed, May 12, 2010 at 2:44 AM, Tom Lane wrote:
> I think what you are describing is a kernel bug. There's not a lot
> we can do about it if the send() call hangs. Considering the kernel
> already knows the connection is closed (per the CLOSE_WAIT state shown
> by netstat) the send() should ret
Andres Freund writes:
> I can reproduce the issue though when the connection just is very, very slow
> (high packet loss). Uppon receiving a signal the send returns with EINTR
> uppon
> which point I think a check for interrupts might be placed.
The gdb trace you showed before gave no indicati
Hi,
On Wednesday 12 May 2010 03:44:16 Tom Lane wrote:
> "Mason Hale" writes:
> > ISSUE: unable to cancel queries using pg_cancel_backend(), that are in
> > send() function call, waiting on client receipt of data.
> I think what you are describing is a kernel bug. There's not a lot
> we can do ab
"Mason Hale" writes:
> ISSUE: unable to cancel queries using pg_cancel_backend(), that are in
> send() function call, waiting on client receipt of data.
I think what you are describing is a kernel bug. There's not a lot
we can do about it if the send() call hangs. Considering the kernel
already
The following bug has been logged online:
Bug reference: 5459
Logged by: Mason Hale
Email address: ma...@onespot.com
PostgreSQL version: 8.3.8
Operating system: Redhat EL 5.1-64 bit
Description:Unable to cancel query while in send()
Details:
ISSUE: unable to cancel
