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 45731D9302 for ; Mon, 19 Sep 2005 13:16:22 -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 15966-01 for ; Mon, 19 Sep 2005 16:16:16 +0000 (GMT) Received: from mail.dialmex.net (67.107.77.98.ptr.us.xo.net [67.107.77.98]) by svr1.postgresql.org (Postfix) with ESMTP id C82F0D9382 for ; Mon, 19 Sep 2005 13:16:15 -0300 (ADT) Received: from david.dialmex.net (dmxnocws13.dialmex.net [67.107.77.78]) by mail.dialmex.net (Postfix) with ESMTP id 71DDDEE98F for ; Mon, 19 Sep 2005 11:16:14 -0500 (CDT) Subject: backend unexpected SIG KILL (9) From: David Stanaway To: pgsql-admin@postgresql.org Content-Type: text/plain Date: Mon, 19 Sep 2005 11:16:14 -0500 Message-Id: <1127146574.2238.6.camel@dmxnocws13.dialmex.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 required=5 tests=[AWL=-0.000, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200509/197 X-Sequence-Number: 18934 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