X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E476C5294A for ; Sat, 23 Apr 2005 12:58:59 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72684-06 for ; Sat, 23 Apr 2005 15:58:50 +0000 (GMT) Received: from window.monsterlabs.com (window.monsterlabs.com [216.183.105.176]) by svr1.postgresql.org (Postfix) with SMTP id B0C42536C1 for ; Sat, 23 Apr 2005 12:58:48 -0300 (ADT) Received: (qmail 9275 invoked from network); 23 Apr 2005 15:58:48 -0000 Received: from host-209.149.56.238.nashville.net (HELO ?10.0.1.2?) (209.149.56.238) by 0 with SMTP; 23 Apr 2005 15:58:48 -0000 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Message-Id: <399c5204777051febd1e3432d981b03b@sitening.com> Content-Transfer-Encoding: quoted-printable Cc: PGSQL Admin From: Thomas F.O'Connell Subject: Killing Processes Date: Sat, 23 Apr 2005 10:58:46 -0500 To: Ken Reid X-Mailer: Apple Mail (2.622) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/342 X-Sequence-Number: 17355 It is generally not recommended that you kill processes with anything=20 stronger than HUP, which is (I believe) what kill sends by default.=20 Stronger signals will cause all backends to kill themselves because of=20= paranoia about data corruption. If the process does not respond to that, then there is no convenient=20 way to kill it. You can correlate processes to queries using the pg_stat_activity view. -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC Strategic Open Source: Open Your i=99 http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Apr 22, 2005, at 6:03 PM, Ken Reid wrote: > Hi Thomas. > > I have been searching high and low and cannot find a way to kill an > individual > user process with Postgres. > > I have tried using a kill -9 to kill a specific process but that=20 > brings the > entire postmaster down. > > This seems to be a very common problem with no answers. > > Would you happen to know how to do this? > > Thanks. > > - Ken=