From: Scott Ribe <scott_ribe@elevated-dev.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: postgres crashes on insert in 40 different threads
Date: Mon, 19 Aug 2013 07:43:28 -0600
Message-ID: <6CDEA2B3-6C42-42D3-BAA8-AF98007012BB@elevated-dev.com> (raw)
In-Reply-To: <52121C56.3020101@postgresql.fr>
References: <CE37F0A6.11842%dzmitry.nikitsin@gmail.com>
<52121C56.3020101@postgresql.fr>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Aug 19, 2013, at 7:23 AM, Stéphane Schildknecht <stephane.schildknecht@postgresql.fr> wrote:
> As Laurenz said, you should have a look at documentation.
>
> It explains how you can lower the risk OOMKiller kills your PostgreSQL processes.
> 1. You can set vm.overcommit_memory to 2 in sysctl.conf
> 2. You can adjust the value of oom_score_adj in startup script to prevent OOMKiller to kill Postmaster
> 3. You can lower shared_buffers, work_mem and max_connections.
4. Use pgbouncer, and radically lower the number of pg connections used.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com
Subject: Re: postgres crashes on insert in 40 different threads
In-Reply-To: <6CDEA2B3-6C42-42D3-BAA8-AF98007012BB@elevated-dev.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