From: | Dzmitry <dzmitry(dot)nikitsin(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: postgres crashes on insert in 40 different threads |
Date: | 2013-08-19 15:01:10 |
Message-ID: | CE380DBF.11999%dzmitry.nikitsin@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)elevated-dev(dot)com> wrote:
>On Aug 19, 2013, at 7:23 AM, Stéphane Schildknecht
><stephane(dot)schildknecht(at)postgresql(dot)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(at)elevated-dev(dot)com
>http://www.elevated-dev.com/
>(303) 722-0567 voice
>
>
>
>
>
>
>--
>Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-admin
From | Date | Subject | |
---|---|---|---|
Next Message | Dzmitry | 2013-08-19 15:07:48 | Re: postgres crashes on insert in 40 different threads |
Previous Message | Frank Lanitz | 2013-08-19 14:59:14 | Re: postgres crashes on insert in 40 different threads |