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 C345AD1D2AC for ; Mon, 2 Feb 2004 12:49:36 +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 81028-01 for ; Mon, 2 Feb 2004 08:49:30 -0400 (AST) Received: from COLSWEEPER.cranel.com (newmail.cranel.com [12.32.71.147]) by svr1.postgresql.org (Postfix) with ESMTP id 1929FD1D6CC for ; Mon, 2 Feb 2004 08:49:26 -0400 (AST) Received: from colmail01.cranel.com (colmail01.cranel.com) by COLSWEEPER.cranel.com (Content Technologies SMTPRS 4.3.12) with ESMTP id for ; Mon, 2 Feb 2004 07:48:27 -0500 Received: by colmail01.cranel.com with Internet Mail Service (5.5.2657.72) id ; Mon, 2 Feb 2004 07:53:15 -0500 Message-ID: <387C22290D3FD71195D300508BF7DB5238AEA9@colmail01.cranel.com> From: "Spiegelberg, Greg" To: 'PGSQL Admin ' Subject: Re: Forcing connections closed Date: Mon, 2 Feb 2004 07:53:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/10 X-Sequence-Number: 12184 If the system in question is ... 1. a Linux or *BSD AND 2. has ipchains/iptables/whatever firewall software installed AND 3. the connections in question to be killed are coming in via port 5432/tcp then I would think you could temporarily change the firewall configuration on the system such that all traffic from the remote IP, or even localhost, on 5432/tcp gets dropped and possibly the connection should drop as well. If it doesn't then you may additionally tweak your tcp_keepalive_time to 0 before changing the firewall rule. Just remember to drop that firewall rule and set the tcp_keepalive_time back when you're done. Just random thoughts. Greg -----Original Message----- From: Juan Miguel To: PGSQL Admin Sent: 2/1/04 4:47 PM Subject: Re: [ADMIN] Forcing connections closed >'kill -9' PID will force all backends to flush cache for no good reason. > >Note that on most unixes, a plain kill PID will send the term signal, >which tells the process to poltely shutdown and release resources. kill >-9 is like using a sledge hammer to swat a fly for this. > > >---------------------------(end of broadcast)--------------------------- >TIP 4: Don't 'kill -9' the postmaster > > > ;-) Yes, you are on the right. "kill -9", is the last try, but often you have to do "kill -9" for killing a procces, even sometimes, 'kill -9' does not work (often when the process is acceding to a hardware device - a CD for example -). ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html