Re: Understand this error - Mailing list pgsql-general

From Dennis Brakhane
Subject Re: Understand this error
Date
Msg-id 226a19190905010140l3acc1b51p31c6f0e407c940d1@mail.gmail.com
Whole thread Raw
In response to Understand this error  (paulo matadr <saddoness@yahoo.com.br>)
List pgsql-general
On Thu, Apr 30, 2009 at 3:00 PM, paulo matadr <saddoness@yahoo.com.br> wrote:
> Hi all,
> my database entry in mode recovery,
> analyzing my pg_log I seem this:
> system logger process (PID 6517) was terminated by signal 9
> background writer process (PID 6519) was terminated by signal 9
> terminating any other active server processes

You are bitten by the OOM-killer. It can lead to severy data loss if it decides
to kill the postmaster. To avoid this, you should always set overcommit_memory
to 2 (which means off). See Section 17.4.3. here:

http://www.postgresql.org/docs/8.3/interactive/kernel-resources.html

You should *never* run a production database server in overcommit_memory mode!

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: 08P01: unexpected EOF on client connection
Next
From: Dave Page
Date:
Subject: Re: Any way to execute ad-hoc pl/pgsql?