On Sun, Apr 28, 2002 at 11:47:19PM -0400, Tom Lane wrote:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > The problem is that sbrk merely extends your memory map, the memory is not
> > actually allocated until it is used, i.e. it's overcomitting memory.
> And this is the application's fault?
> If Linux overcommits memory, then Linux is broken. Do not bother to
> argue the point. I shall recommend other Unixen to anyone who wants
> to run reliable applications. (HPUX for example; which has plenty of
> faults, but at least it keeps track of how much space it can promise.)
I'm not saying it's a good idea. Indeed, people saying all the time it's
bad. But it is the default. If people don't like then they should set the
over_commit sysctl off (I forget the exact name).
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Canada, Mexico, and Australia form the Axis of Nations That
> Are Actually Quite Nice But Secretly Have Nasty Thoughts About America
In response to
pgsql-general by date
|Next:||From: Steve Lane||Date: 2002-04-29 05:35:38|
|Subject: Postgres utils chewing RAM|
|Previous:||From: Michael Loftis||Date: 2002-04-29 04:39:03|
|Subject: Re: OIDs|