X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 91316D1CACB for ; Sun, 15 Feb 2004 05:34:37 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 23506-03 for ; Sun, 15 Feb 2004 01:34:41 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id BB1FCD1C7F7 for ; Sun, 15 Feb 2004 01:34:34 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1F5Ye6W005632; Sun, 15 Feb 2004 00:34:40 -0500 (EST) To: Rune Froysa Cc: pgsql-admin@postgresql.org Subject: Re: Server-side killing of database connection (7.3.4) In-reply-to: References: Comments: In-reply-to Rune Froysa message dated "13 Feb 2004 10:11:37 +0100" Date: Sun, 15 Feb 2004 00:34:39 -0500 Message-ID: <5631.1076823279@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/219 X-Sequence-Number: 12393 Rune Froysa writes: > I need to kill a connected database user. I'm able to find the pid > associated with the troublesome user. However, if I try killing the > process with any of INT, TERM or QUIT, all connected database users > get the message: > WARNING: Message from PostgreSQL backend: > The Postmaster has informed me that some other backend > died abnormally and possibly corrupted shared memory. > I have rolled back the current transaction and am > going to terminate your database system connection and exit. > Please reconnect to the database system and repeat your query. Better take another look at how you're doing that kill. It is not sending the signal number you think it is. regards, tom lane