From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Linux2.6 overcommit behaviour |
Date: | 2003-08-28 11:41:52 |
Message-ID: | 3F4DEA80.60607@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yes, in 2.6, which is not yet released. Even after it is released I
expect it to take some time to bed down and make its way into vendor
releases, if the history of 2.4 is anything to go by.
Incidentally, it looks to me like it is only in 2.6 if your kernel is
built with CONFIG_SECURITY, which I expect most will be.
andrew
Shridhar Daithankar wrote:
>Hi all,
>
>Following is from Documentation/vm/overcommit-accounting
>-------------
>2 - (NEW) strict overcommit. The total address space commit
> for the system is not permitted to exceed swap + a
> configurable percentage (default is 50) of physical RAM.
> Depending on the percentage you use, in most situations
> this means a process will not be killed while accessing
> pages but will receive errors on memory allocation as
> appropriate.
>-------------
>
>Looks like it's been taken care once for all.
>
> Shridhar
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-08-28 11:52:36 | Re: Linux2.6 overcommit behaviour |
Previous Message | Larry Rosenman | 2003-08-28 11:19:54 | Re: Beta2 Tag'd and Bundled ... |