Erik Jones wrote:
On Sep 10, 2008, at 5:57 AM, Tommy Gildseth wrote:
Tom Lane wrote:
Tommy Gildseth [EMAIL PROTECTED] writes:
Richard Huxton wrote:
For what it's worth, I've run into a situation similar to this with a
client a couple time in the last week or two (I can't say identical as
I have a query on a database that has been running for nearly 24 hours
at the moment. The query itself doesn't seem like it should take very
long to run, so it seems like there's something else going on here.
The output from pg_stat_activity looks like this:
SELECT procpid, waiting,
Richard Huxton wrote:
Tommy Gildseth wrote:
SELECT pg_cancel_backend(17504) has no effect, neither does kill 17504
from the shell.
Strange.
I tried strace -p17504, and this gave me just the following output:
sendto(7, \7\0\0\0\003771\0\0\0\00224\0\0\0\017127.120.213.18..., 968,
0, NULL, 0
Tommy Gildseth [EMAIL PROTECTED] writes:
Richard Huxton wrote:
Looks like part of your query results being sent. Is it hung in that one
system-call?
Yes, I left it there for about ~1 hour, and that was all that ever came.
Seems like you have got a network issue. What does netstat show for
Tom Lane wrote:
Tommy Gildseth [EMAIL PROTECTED] writes:
Richard Huxton wrote:
Looks like part of your query results being sent. Is it hung in that one
system-call?
Yes, I left it there for about ~1 hour, and that was all that ever came.
Seems like you have got a network issue. What does
On Sep 10, 2008, at 5:57 AM, Tommy Gildseth wrote:
Tom Lane wrote:
Tommy Gildseth [EMAIL PROTECTED] writes:
Richard Huxton wrote:
Looks like part of your query results being sent. Is it hung in
that one
system-call?
Yes, I left it there for about ~1 hour, and that was all that ever
