Обсуждение: Re: [ADMIN] Dangerous hint in the PostgreSQL manual
Listaccount wrote: > Hello > > I have been trapped by the advice from the manual to use "sysctl -w > vm.overcommit_memory=2" when using Linux (see 16.4.3. Linux Memory > Overcommit). This value should only be used when PostgreSQL is the only > Application running on the machine in question. It should be checked > against the values "CommitLimit" and "Committed_AS" in /proc/meminfo on > a longer running system. If "Committed_AS" reaches or come close to > "CommitLimit" one should not set overcommit_memory=2 (see > http://www.redhat.com/archives/rhl-devel-list/2005-February/msg00738.html). > I think it should be included in the manual as a warning because with > this setting the machine in question may get trouble with "fork failed" > even if the standard system tools report a lot of free memory causing > confusion to the admins. This discussion belongs on -docs... moving. Joshua D. Drake > > Regards > > Andreas > > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >