On Fri, Aug 3, 2012 at 12:08 PM, Radovan Jablonovsky <radovan.jablonovsky@xxxxxxxxxxxx> wrote: > Thanks you for your response. > > Database config: > shared_buffers = 8GB > temp_buffers = 32MB > work_mem = 64MB > maintenance_work_mem = 512MB > effective_cache_size = 16GB > > In usual load there are not much pressure on memory, but it is possible to > have all clients start using heavy reports. They are valid requests and > could consume all memory. In this border and not likely but possible > scenario it could be useful to let OOM killer to kill client's > processes/connections but leave PostgreSQL system processes (postmaster, > writer, stat, log, streaming, ...) excluded from reach of OOM killer. You're only realistic solution is to either limit the incoming connections via a connection pooler like pgbouncer or to lower your work_mem to something smaller. What's you're current max connections setting? -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
