Re: Killing a child process - Mailing list pgsql-admin

From David Stanaway
Subject Re: Killing a child process
Date
Msg-id 1018933616.1888.30.camel@debian
Whole thread Raw
In response to Re: Killing a child process  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Mon, 2002-04-15 at 19:28, Tom Lane wrote:
> "Bojan Belovic" <bbelovic@usa.net> writes:
> > Every once in a while I'll spot a query that is taking unusually long time
> > to run (a chiled process that keeps the processor at 100% for like 3
> > minutes). Is there a way to see the queries currently executing
>
> ps, top?  Also see the stats views, if you are running 7.2.
>
> > and/or kill
> > a single process without affecting the operation of the server
>
> kill -INT to a backend will issue a query cancel, which is pretty safe.


There is also pgmonitor (Which I think is in contrib) which shows the
stats on the current backend processes (Works on 7.1.3 for me) and is
much nicer for working out whats using CPU, and the query that is
causing the problem.

--
David Stanaway

Attachment

pgsql-admin by date:

Previous
From: "Dan MacNeil"
Date:
Subject: Re: psql command line history not working
Next
From: Jean-Arthur Silve
Date:
Subject: Vacuum blocking...