User-Agent: Microsoft-MacOutlook/14.2.3.120616
Date: Mon, 19 Aug 2013 18:01:10 +0300
Subject: Re: postgres crashes on insert in 40 different threads
From: Dzmitry <dzmitry.nikitsin@gmail.com>
To: Scott Ribe <scott_ribe@elevated-dev.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <CE380DBF.11999%dzmitry.nikitsin@gmail.com>
Thread-Topic: [ADMIN] postgres crashes on insert in 40 different threads
In-Reply-To: <6CDEA2B3-6C42-42D3-BAA8-AF98007012BB@elevated-dev.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

I am already using pgpool, is it bad have 550 connections, is it much ?
Thank you guys for all your help.

Thanks,
  Dzmitry


On 8/19/13 4:43 PM, "Scott Ribe" <scott_ribe@elevated-dev.com> wrote:

>On Aug 19, 2013, at 7:23 AM, St=E9phane Schildknecht
><stephane.schildknecht@postgresql.fr> wrote:
>
>> As Laurenz said, you should have a look at documentation.
>>=20
>> 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.
>
>--=20
>Scott Ribe
>scott_ribe@elevated-dev.com
>http://www.elevated-dev.com/
>(303) 722-0567 voice
>
>
>
>
>
>
>--=20
>Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-admin


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin