| From: | Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: "Stuck" query |
| Date: | 2008-09-11 06:49:22 |
| Message-ID: | 48C8BF72.80704@usit.uio.no |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Erik Jones wrote:
>
> On Sep 10, 2008, at 5:57 AM, Tommy Gildseth wrote:
>
>> Tom Lane wrote:
>>> Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no> 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
> don't know all of the details about the client end of your connection).
> Using the client port # you can use lsof in addition to netstat (lsof -i
> tcp:49004) to track down the client process. In our case, the client
> process was a connection made via an ssh tunnel and was sitting in
> FIN_WAIT2 status. Killing the client process individually made
> everything go away nicely without any kind of extra downtime necessary.
Thanks, I'll keep that in mind if/when it happens again.
--
Tommy Gildseth
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2008-09-11 07:29:56 | Re: postgres user account on OSX |
| Previous Message | Tobias Anstett | 2008-09-11 06:42:07 | How to check if an array is empty |