|
Home > Archive > PostgreSQL Administration > September 2005 > backend unexpected SIG KILL (9)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
backend unexpected SIG KILL (9)
|
|
| David Stanaway 2005-09-19, 1:25 pm |
| 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
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Scott Marlowe 2005-09-19, 1:25 pm |
| 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.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
|
|
|
|
|