pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
backend unexpected SIG KILL (9)
2+ messages / 2 participants
[nested] [flat]

* backend unexpected SIG KILL (9)
@ 2005-09-19 16:16  David Stanaway <david@stanaway.net>
  0 siblings, 1 reply; 2+ messages in thread

From: David Stanaway @ 2005-09-19 16:16 UTC (permalink / raw)
  To: 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





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: backend unexpected SIG KILL (9)
@ 2005-09-19 16:38  Scott Marlowe <smarlowe@g2switchworks.com>
  parent: David Stanaway <david@stanaway.net>
  0 siblings, 0 replies; 2+ messages in thread

From: Scott Marlowe @ 2005-09-19 16:38 UTC (permalink / raw)
  To: David Stanaway <david@stanaway.net>; +Cc: 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.



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2005-09-19 16:38 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-09-19 16:16 backend unexpected SIG KILL (9) David Stanaway <david@stanaway.net>
2005-09-19 16:38 ` Scott Marlowe <smarlowe@g2switchworks.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox