Skip site navigation (1) Skip section navigation (2)

Re: backend unexpected SIG KILL (9)

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: David Stanaway <david(at)stanaway(dot)net>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: backend unexpected SIG KILL (9)
Date: 2005-09-19 16:38:31
Message-ID: 1127147911.30120.100.camel@state.g2switchworks.com (view raw or flat)
Thread:
Lists: pgsql-admin
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.

In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2005-09-19 16:52:44
Subject: Re: Backup issue
Previous:From: David StanawayDate: 2005-09-19 16:16:14
Subject: backend unexpected SIG KILL (9)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group