Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 83FEF2E0074 for ; Tue, 22 Apr 2008 13:07:10 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 99064-04 for ; Tue, 22 Apr 2008 13:06:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id A5DAF2E0078 for ; Tue, 22 Apr 2008 13:06:59 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m3MG6wun022377 for ; Tue, 22 Apr 2008 12:06:58 -0400 (EDT) To: pgsql-admin@postgresql.org Subject: Re: Server Crash In-reply-to: References: Comments: In-reply-to "Hajek, Nick" message dated "Tue, 22 Apr 2008 10:39:51 -0500" Date: Tue, 22 Apr 2008 12:06:58 -0400 Message-ID: <22376.1208880418@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/228 X-Sequence-Number: 28992 > From: Scott Marlowe [mailto:scott.marlowe@gmail.com] >> Kill -9 is the "shoot it in the head" signal. It is not >> generated by postgresql in normal operation. It can be >> generated by "pg_ctl -m immediate stop" . At least I think >> that's what signal it sends. Just for the archives: Postgres never generates kill -9 at all. (Immediate stop uses SIGQUIT, instead.) When you see that in the log, you can be sure it was a manual action or the OOM killer. regards, tom lane