X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A98629FA2C7 for ; Tue, 2 May 2006 20:30:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 76328-01 for ; Tue, 2 May 2006 20:30:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 53E969FAA6E for ; Tue, 2 May 2006 20:30:02 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k42NU083006446; Tue, 2 May 2006 19:30:00 -0400 (EDT) To: Dan Harris cc: PostgreSQL Performance Subject: Re: Killing long-running queries In-reply-to: <4457E918.10007@drivefaster.net> References: <4457E918.10007@drivefaster.net> Comments: In-reply-to Dan Harris message dated "Tue, 02 May 2006 17:19:52 -0600" Date: Tue, 02 May 2006 19:30:00 -0400 Message-ID: <6445.1146612600@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/61 X-Sequence-Number: 18848 Dan Harris writes: > So, I have been searching for a way to kill an individual query. I read > in the mailing list archives that you could 'kill' the pid. I've tried > this a few times and more than once, it has caused the postmaster to > die(!), terminating every query that was in process, even unrelated to > that query. You should be using SIGINT, not SIGTERM. regards, tom lane