Re: killing process question

--howdy:

--that's just it: it's not doing a lot of anything.
--not munching on CPU cycles or anything like that.
--'ps auwx' shows that the process is stopped
--(displays a 'T' in the line, i. e.:)

[snip]
postgres 3488 5.3 0.0 11412 4 pts/4 T Sep18 88:53 postgres: joe
testdb 16.xx.xx.xx SELECT
[/snip]

--to clarify, the pid 3488 is the backend connection to the
--database that i should be killing, right? that's what i've
--BEEN killing, so, if i am missing something, steer me in the
--right way, please.

--having said that, there are processes that does NOT have
--the 'T' (stopped) code (just 'S' - sleep ... i have yet
--to see any 'Z' zombie processes). some of these are
--also no-responsive to the user or to me trying to use
--kill <pid>.

--any suggestions?

-X

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]

"Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> writes:
> --okay, but the client has since terminated
> --it's session (if i understand you correctly).
> --is this just something that will just have to
> --hang around until i shutdown the database / boot
> --the machine?

I dunno. Are you sure this is a backend process? What is it doing
(or not doing) ... is it chewing any CPU cycles? What status does it
show in ps?

regards, tom lane