From: Scott Marlowe <smarlowe@g2switchworks.com>
To: David Stanaway <david@stanaway.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: backend unexpected SIG KILL (9)
Date: Mon, 19 Sep 2005 11:38:31 -0500
Message-ID: <1127147911.30120.100.camel@state.g2switchworks.com> (raw)
In-Reply-To: <1127146574.2238.6.camel@dmxnocws13.dialmex.net>
References: <1127146574.2238.6.camel@dmxnocws13.dialmex.net>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, david@stanaway.net
Subject: Re: backend unexpected SIG KILL (9)
In-Reply-To: <1127147911.30120.100.camel@state.g2switchworks.com>
References: <1127146574.2238.6.camel@dmxnocws13.dialmex.net> <1127147911.30120.100.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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