From: | Dennis Brakhane <brakhane(at)googlemail(dot)com> |
---|---|
To: | paulo matadr <saddoness(at)yahoo(dot)com(dot)br> |
Cc: | GENERAL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Understand this error |
Date: | 2009-05-01 08:40:47 |
Message-ID: | 226a19190905010140l3acc1b51p31c6f0e407c940d1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 30, 2009 at 3:00 PM, paulo matadr <saddoness(at)yahoo(dot)com(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-05-01 09:30:02 | Re: Any way to execute ad-hoc pl/pgsql? |
Previous Message | Craig Ringer | 2009-05-01 06:31:48 | Re: 08P01: unexpected EOF on client connection |