[Groonga-mysql-commit] mroonga/mroonga.github.com at c3d2a4e [master] blog en: add link to document

Back to archive index

HAYASHI Kentaro null+****@clear*****
Tue Apr 28 11:26:36 JST 2015


HAYASHI Kentaro	2015-04-28 11:26:36 +0900 (Tue, 28 Apr 2015)

  New Revision: c3d2a4e12af9837d2dba14e026e9b8036d17dd0f
  https://github.com/mroonga/mroonga.github.com/commit/c3d2a4e12af9837d2dba14e026e9b8036d17dd0f

  Message:
    blog en: add link to document

  Modified files:
    en/_posts/2015-04-29-release.md

  Modified: en/_posts/2015-04-29-release.md (+1 -1)
===================================================================
--- en/_posts/2015-04-29-release.md    2015-04-28 11:21:49 +0900 (e19a783)
+++ en/_posts/2015-04-29-release.md    2015-04-28 11:26:36 +0900 (e4f4f6e)
@@ -53,7 +53,7 @@ It is nonsense that calculating statistical information affects to total executi
 
 If Mroonga executes query too slow in range search, and "show profile" indicates that statistics occupies most of execution time, that's it. We recommends to upgrade to Mroonga 5.02.
 
-Additionally, we added mroonga_max_n_records_for_estimate server environment variable. It limits to max estimated records in range. The default value of this variable is 1000. Note that the value of this variable affects whether which index is used or not.
+Additionally, we added [mroonga_max_n_records_for_estimate](/docs/reference/server_variables.html#mroonga-max-n-records-for-estimate) server environment variable. It limits to max estimated records in range. The default value of this variable is 1000. Note that the value of this variable affects whether which index is used or not.
 
 ### Conclusion
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-mysql-commit mailing list
Back to archive index