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 D6DF5474E71 for ; Fri, 12 Jul 2002 22:13:15 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g6D2DBX02816; Fri, 12 Jul 2002 22:13:11 -0400 (EDT) From: Bruce Momjian Message-Id: <200207130213.g6D2DBX02816@candle.pha.pa.us> Subject: Re: Query kill In-Reply-To: <3D2F1798.E65AC418@Yahoo.com> To: Jan Wieck Date: Fri, 12 Jul 2002 22:13:11 -0400 (EDT) Cc: Rudi Starcevic , 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/197 X-Sequence-Number: 8576 Jan Wieck wrote: > Bruce Momjian wrote: > > > > 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. > > Doesn't the client need a signal handler for that and call > PQcancelRequest() in that? Every backend has that signal handler defined, I think. -- 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