From: David Stanaway <david@stanaway.net>
To: pgsql-admin@postgresql.org
Subject: backend unexpected SIG KILL (9)
Date: Mon, 19 Sep 2005 11:16:14 -0500
Message-ID: <1127146574.2238.6.camel@dmxnocws13.dialmex.net> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: david@stanaway.net
Subject: Re: backend unexpected SIG KILL (9)
In-Reply-To: <1127146574.2238.6.camel@dmxnocws13.dialmex.net>
References: <1127146574.2238.6.camel@dmxnocws13.dialmex.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox