Memory Overcommit

From: Andy Chambers <achambers(at)mcna(dot)net>
To: pgsql <pgsql-general(at)postgresql(dot)org>
Subject: Memory Overcommit
Date: 2012-06-07 15:33:21
Message-ID: CAAfW55pv3TcoTmvm2f2aKS2G6tw3VU2Pdtq8kpb3hQaVMz36VQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi All,

We've just run into the dreaded "OOM Killer". I see that on Linux
>2.6, it's recommended to turn off memory overcommit. I'm trying to
understand the implications of doing this. The interweb says this
means that forking servers can't make use of "copy on write"
semantics. Is this true? Does it matter for a server running just
postgres?

--
Andy Chambers
Software Engineer
(e) achambers(at)mcna(dot)net
(t) 954-682-0573

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-06-07 16:14:30 Re: Memory Overcommit
Previous Message Benson Jin 2012-06-07 15:29:59 Re: Need help in transferring FP to Int64 DateTime