Tom Lane wrote:
> "Craig A. James" <cjames@modgraph-usa.com> writes:
>> Here's something I found googling for "memory overcommitment"+linux
>> http://archives.neohapsis.com/archives/postfix/2000-04/0512.html
>
> That might have been right when it was written (note the reference to a
> 2.2 Linux kernel), but it's 100% wrong now. 0 is the default, not-safe
> setting.
Is this something we could detect and show a warning for at initdb
time; or perhaps log a warning in the log files at postmaster startup?
This dangerous choice of settings seems to catch quite a few postgresql
users.