Memory Overcommit - Mailing list pgsql-general

From Andy Chambers
Subject Memory Overcommit
Date
Msg-id CAAfW55pv3TcoTmvm2f2aKS2G6tw3VU2Pdtq8kpb3hQaVMz36VQ@mail.gmail.com
Whole thread Raw
Responses Re: Memory Overcommit
List 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@mcna.net
(t) 954-682-0573

pgsql-general by date:

Previous
From: Condor
Date:
Subject: Two databases on the same server, looking for idea how to restrict access.
Next
From: Tom Lane
Date:
Subject: Re: Memory Overcommit