Re: Killing a child process

From: David Stanaway <david(at)stanaway(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Killing a child process
Date: 2002-04-16 05:06:55
Message-ID: 1018933616.1888.30.camel@debian
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, 2002-04-15 at 19:28, Tom Lane wrote:
> "Bojan Belovic" <bbelovic(at)usa(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Darley 2002-04-16 06:46:30 Re: ODBC Problem
Previous Message Peter Darley 2002-04-16 03:41:26 ODBC Problem