backend unexpected SIG KILL (9) - Mailing list pgsql-admin

From David Stanaway
Subject backend unexpected SIG KILL (9)
Date
Msg-id 1127146574.2238.6.camel@dmxnocws13.dialmex.net
Whole thread Raw
Responses Re: backend unexpected SIG KILL (9)  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-admin
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



pgsql-admin by date:

Previous
From: "Gandeed Phanibhushan Rao-A18356"
Date:
Subject: PostgreSQL configuration problem
Next
From: Scott Marlowe
Date:
Subject: Re: backend unexpected SIG KILL (9)