From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_cancel_backend() does not work with buzz queries |
Date: | 2007-10-23 07:35:04 |
Message-ID: | 20071023073504.GA10684@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-ru-general |
On Tue, Oct 23, 2007 at 09:56:26AM +0400, Sergey Konoplev wrote:
> I took a look at TCP state with netstat:
>
> pgdb:/base/PG-Data # netstat -pna |grep 8590
> tcp 1 0 127.0.0.1:5432 127.0.0.1:35442
> CLOSE_WAIT 8590/postgres: kono
CLOSE_WAIT means that the client (in this case SSH) has shutdown() its
end of the connection and evidently postgresql hasn't noticed. However,
SSH has not closed its socket entirely, because then the write would
fail.
Can you strace the SSH daemon, my bet is that it's also stuck on a
write(), to the original client. It would also be interesting to know
what the original client is doing, since it's obviously still alive.
Looks like somewhere along the chain a program called shutdown() but is
no longer reading incoming data...
Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Martinez | 2007-10-23 07:56:41 | alter database tablespace |
Previous Message | Ow Mun Heng | 2007-10-23 06:02:14 | Determine query run-time from pg_* tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2007-10-23 11:53:06 | Re: pg_cancel_backend() does not work with buzz queries |
Previous Message | Sergey Konoplev | 2007-10-23 06:08:49 | Re: Fwd: pg_cancel_backend() не снимает зависшие транзакции |