On Aug 19, 2013, at 7:23 AM, Stéphane Schildknecht <stephane.schildknecht@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxx http://www.elevated-dev.com/ (303) 722-0567 voice -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
