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 6D80AD1B8CE for ; Fri, 13 Feb 2004 09:11:50 +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 01163-05 for ; Fri, 13 Feb 2004 05:11:44 -0400 (AST) Received: from pat.uio.no (pat.uio.no [129.240.130.16]) by svr1.postgresql.org (Postfix) with ESMTP id 532A6D1D2F7 for ; Fri, 13 Feb 2004 05:11:42 -0400 (AST) Received: from mail-mx6.uio.no ([129.240.10.47]) by pat.uio.no with esmtp (Exim 4.20) id 1ArZMN-0007I4-95 for pgsql-admin@postgresql.org; Fri, 13 Feb 2004 10:11:43 +0100 Received: from dresden.uio.no ([129.240.186.146]) by mail-mx6.uio.no with esmtp (Exim 4.14) id 1ArZMI-0002vd-7I for pgsql-admin@postgresql.org; Fri, 13 Feb 2004 10:11:38 +0100 Received: from runefro by dresden.uio.no with local (Exim 2.12 #1) id 1ArZMI-00033K-00 for pgsql-admin@postgresql.org; Fri, 13 Feb 2004 10:11:38 +0100 To: pgsql-admin@postgresql.org Subject: Server-side killing of database connection (7.3.4) From: Rune Froysa Date: 13 Feb 2004 10:11:37 +0100 Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning X-UiO-MailScanner: No virus found X-UiO-Spam-info: not spam, SpamAssassin (score=0, required 12) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/215 X-Sequence-Number: 12389 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. Is it possible to kill a connected user without shuting down the database? I.e. something like "alter system kill session" in oracle. Regards, Rune Frøysa