Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net
	[216.55.132.35])
	by postgresql.org (Postfix) with ESMTP id E6C29475873
	for <pgsql-sql@postgresql.org>; Fri, 12 Jul 2002 01:01:37 -0400 (EDT)
Received: (from pgman@localhost)
	by candle.pha.pa.us (8.11.6/8.10.1) id g6C51Vo14062;
	Fri, 12 Jul 2002 01:01:31 -0400 (EDT)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200207120501.g6C51Vo14062@candle.pha.pa.us>
Subject: Re: Query kill
In-Reply-To: <3D2E6283.4090101@oasis.net.au>
To: Rudi Starcevic <rudi@oasis.net.au>
Date: Fri, 12 Jul 2002 01:01:31 -0400 (EDT)
Cc: pgsql-sql@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL99 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Archive-Number: 200207/176
X-Sequence-Number: 8555

Rudi Starcevic wrote:
> Hello,
> 
> If I write a query that is inefficient or in an eternal loop how
> do I stop it without restarting the postmaster ?
> 
> I can see many postmaster processed appearing in the output of the 'ps' 
> command.
> Do I need to stop/kill them all or can I stop just the query I want ?

Just send a SIGINT to the process. That simulates a ^C, which works too
from the client like psql.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026