Re: [PATCHES] improve overcommit docs
Andrew Dunstan [EMAIL PROTECTED] writes: At the time I wrote the original 2.6 was not out even in prerelease, which is why I was deliberately somewhat vague about it. It is still in prerelease, and it will in fact work slightly differently from what was in some 2.4 kernels - there are 2 settings that govern this instead of 1. Okay, I revised that section yet again based on this info: http://candle.pha.pa.us/main/writings/pgsql/sgml/kernel-resources.html#AEN17043 Thanks for the update. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] improve overcommit docs
That covers it extremely well. cheers andrew Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: At the time I wrote the original 2.6 was not out even in prerelease, which is why I was deliberately somewhat vague about it. It is still in prerelease, and it will in fact work slightly differently from what was in some 2.4 kernels - there are 2 settings that govern this instead of 1. Okay, I revised that section yet again based on this info: http://candle.pha.pa.us/main/writings/pgsql/sgml/kernel-resources.html#AEN17043 Thanks for the update. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] improve overcommit docs
Neil Conway [EMAIL PROTECTED] writes: This patch makes some improvements to the section of the documentation that describes the Linux 2.4 memory overcommit behavior. Applied. I tweaked some of the wording a bit further. I removed the almost content-free assertion that You will need enough swap space to cover your memory needs. If this is intended to communicate anything meaningful, can someone rephrase it, please? Seemed pretty content-free to me too. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
