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 1C01FD1D613 for ; Sun, 1 Feb 2004 21:48:57 +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 19097-07 for ; Sun, 1 Feb 2004 17:48:46 -0400 (AST) Received: from mta03.ono.com (unknown [62.42.230.12]) by svr1.postgresql.org (Postfix) with ESMTP id 7EEA7D1B462 for ; Sun, 1 Feb 2004 17:48:43 -0400 (AST) Received: from ono.com (62.42.97.126) by mta03.ono.com (7.0.024) id 3FC7B661002594B6 for pgsql-admin@postgresql.org; Sun, 1 Feb 2004 22:47:38 +0100 Message-ID: <401D73FA.1070808@ono.com> Date: Sun, 01 Feb 2004 22:47:38 +0100 From: Juan Miguel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: es-es, en-us, en MIME-Version: 1.0 To: PGSQL Admin Subject: Re: Forcing connections closed References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/2 X-Sequence-Number: 12176 >'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 -).