X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2BBBFD93E7 for ; Mon, 19 Sep 2005 13:38:48 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 21531-01 for ; Mon, 19 Sep 2005 16:38:37 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id AD7C9D93DC for ; Mon, 19 Sep 2005 13:38:34 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 19 Sep 2005 11:38:31 -0500 Subject: Re: backend unexpected SIG KILL (9) From: Scott Marlowe To: David Stanaway Cc: pgsql-admin@postgresql.org In-Reply-To: <1127146574.2238.6.camel@dmxnocws13.dialmex.net> References: <1127146574.2238.6.camel@dmxnocws13.dialmex.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1127147911.30120.100.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 19 Sep 2005 11:38:31 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200509/198 X-Sequence-Number: 18935 On Mon, 2005-09-19 at 11:16, David Stanaway wrote: > Why would the backend get a KILL signal like this? It was doing a > routine select ... into , or a copy ... to at the time. > > > 2005-09-19 09:52:46 [1511] LOG: server process (PID 19446) was > terminated by signal 9 > 2005-09-19 09:52:46 [1511] LOG: terminating any other active server > processes > 2005-09-19 09:52:46 [1712] WARNING: terminating connection because of > crash of another server process > DETAIL: The postmaster has commanded this server process to roll back > the current transaction and exit, because another server process exited > abnormally and possibly corrupted shared memory. > HINT: In a moment you should be able to reconnect to the database and > repeat your command. > > > Debian 7.4.3 package > Version: 7.4.3-3 More than likely some system memory limit was hit and the linux OOM killer kicked in and started killing processes. Unfortunately, it tends to kill things using a lot memory to free up as much as possible.