backend unexpected SIG KILL (9)

From: David Stanaway <david(at)stanaway(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: backend unexpected SIG KILL (9)
Date: 2005-09-19 16:16:14
Message-ID: 1127146574.2238.6.camel@dmxnocws13.dialmex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2005-09-19 16:38:31 Re: backend unexpected SIG KILL (9)
Previous Message Gandeed Phanibhushan Rao-A18356 2005-09-19 13:31:03 PostgreSQL configuration problem