Re: postgres crashes on insert in 40 different threads
| От | Scott Ribe |
|---|---|
| Тема | Re: postgres crashes on insert in 40 different threads |
| Дата | |
| Msg-id | 6CDEA2B3-6C42-42D3-BAA8-AF98007012BB@elevated-dev.com обсуждение исходный текст |
| Ответ на | Re: postgres crashes on insert in 40 different threads (Stéphane Schildknecht<stephane.schildknecht@postgresql.fr>) |
| Ответы |
Re: postgres crashes on insert in 40 different threads
|
| Список | pgsql-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
В списке pgsql-admin по дате отправления: