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  LOG: server process (PID 19446) was
> terminated by signal 9
> 2005-09-19 09:52:46  LOG: terminating any other active server
> 2005-09-19 09:52:46  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.
In response to
pgsql-admin by date
|Next:||From: Scott Marlowe||Date: 2005-09-19 16:52:44|
|Subject: Re: Backup issue|
|Previous:||From: David Stanaway||Date: 2005-09-19 16:16:14|
|Subject: backend unexpected SIG KILL (9)|