From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: killing process question |
Date: | 2002-09-19 14:44:55 |
Message-ID: | 3D8A303F.7528.1460B376@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 19 Sep 2002 at 10:39, Johnson, Shaunn wrote:
>
> --thanks for the reply:
>
> --no, I don't see anything like that. this is what I have:
>
> [snip]
>
> postgres 3488 5.6 0.0 11412 4 pts/4 T Sep18 88:53 postgres:
> joetestdb 16.xx.xx.xx SELECT
> [/snip]
>
> --this tells me that this proc had been running once upon a time (since the
> 18th) and
> --has stopped (the 'T'). the user has said that he had since killed the tool
> --that connected to the database and booted his machine.
>
> --so ... when I do a 'kill pid' or 'kill -TERM pid' ... *poof* ... nothing
> happens ...
Does restarting database helps? It may just make the thing go away..
Or stop the database, kill the pid with -9 and start it again.. Nothing lost..
Bye
Shridhar
--
Shedenhelm's Law: All trails have more uphill sections than they have downhill
sections.
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Harding | 2002-09-19 14:47:16 | Re: Memory Errors... |
Previous Message | Tom Lane | 2002-09-19 14:43:40 | Re: array issue.... |