Re: PostgreSQL 7.3.4 gets killed by SIG_KILL

From: Jeff <threshar(at)torgo(dot)978(dot)org>
To: "Magnus Naeslund(t)" <mag(at)fbab(dot)net>
Cc: doug(at)mcnaught(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL 7.3.4 gets killed by SIG_KILL
Date: 2003-12-04 13:00:14
Message-ID: 20031204080014.58d0381a.threshar@torgo.978.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 04 Dec 2003 03:35:49 +0100
"Magnus Naeslund(t)" <mag(at)fbab(dot)net> wrote:

>
> Well this just isn't the case.
> There is no printout in kernel logs/dmesg (as it would be if the
> kernel killed it in an OOM situation).
> I have 1 GB of RAM, and 1.5 GB of swap (swap never touched).
>

Do you have any system monitoring scripts that may be killing it as it
may look like a "runaway" process?

We've had this happen to us before. You tend to forget about things like
that.

--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Doug McNaught 2003-12-04 13:02:10 Re: PostgreSQL 7.3.4 gets killed by SIG_KILL
Previous Message Alvaro Herrera 2003-12-04 12:21:37 Re: request for feedback - read-only GUC variables, pg_settings