From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Hervé Piedvache <herve(at)elma(dot)fr>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Big trouble with memory !! |
Date: | 2005-04-06 20:37:59 |
Message-ID: | 5905.1112819879@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> What I don't understand is the problem with overcommitting.
The problem with Linux overcommit is that when the kernel does run out
of memory, the process it chooses to kill isn't necessarily one that was
using an unreasonable amount of memory. The earlier versions were quite
willing to kill "init" ;-) ... I think they hacked it to prevent that
disaster, but it's still entirely capable of deciding to take out the
(real) postmaster, your mail daemon, or other processes you'd prefer not
to lose. As such, the feature is really too dangerous to enable on
machines being used for production purposes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-04-06 20:40:28 | Re: lower function |
Previous Message | Tom Lane | 2005-04-06 20:30:44 | Re: Problems with Set Returning Functions (SRFs) |