rroonga 3.0.8-x64-mingw32 → 3.0.9-x64-mingw32

data/vendor/local/share/man/man1/groonga.1

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "September 27, 2013" "3.0.8" "groonga"
+.TH "GROONGA" "1" "October 28, 2013" "3.0.9" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -34,14 +34,6 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fBnews\fP
 .UNINDENT
-.sp
-\fBNOTE:\fP
-.INDENT 0.0
-.INDENT 3.5
-This document is also ditributed in forms of release source archive and updated time to time.
-If you want to refer latest documentation in source form, you can view such files via GitHub repository browser (\fI\%https://github.com/groonga/groonga/tree/master/doc/source\fP).
-.UNINDENT
-.UNINDENT
 .SH CHARACTERISTICS OF GROONGA
 .SS Groonga overview
 .sp
@@ -122,7 +114,7 @@ Start command prompt \fBcmd.exe\fP and download x86 executable binary by default
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.8\-x86.exe
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.9\-x86.exe
 .ft P
 .fi
 .UNINDENT
@@ -138,7 +130,7 @@ Start command prompt \fBcmd.exe\fP and download x64 executable binary by default
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.8\-x64.exe
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.9\-x64.exe
 .ft P
 .fi
 .UNINDENT
@@ -159,7 +151,7 @@ Start command prompt \fBcmd.exe\fP and download x86 zip archive by default brows
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.8\-x86.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.9\-x86.zip
 .ft P
 .fi
 .UNINDENT
@@ -175,7 +167,7 @@ Start command prompt \fBcmd.exe\fP and download x64 zip archive by default brows
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.8\-x64.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.9\-x64.zip
 .ft P
 .fi
 .UNINDENT
@@ -211,7 +203,7 @@ Visual Studio 2010 Express and download it by default browser:
 .nf
 .ft C
 > cd c:\eUsers\e%USERNAME%\eDownloads
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/source/groonga/groonga\-3.0.8.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/source/groonga/groonga\-3.0.9.zip
 .ft P
 .fi
 .UNINDENT
@@ -225,7 +217,7 @@ Move to the groonga\(aqs source folder:
 .sp
 .nf
 .ft C
-> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.0.8
+> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -239,7 +231,7 @@ parameter instead:
 .sp
 .nf
 .ft C
-groonga\-3.0.8> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
+groonga\-3.0.9> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
 .ft P
 .fi
 .UNINDENT
@@ -251,7 +243,7 @@ Build:
 .sp
 .nf
 .ft C
-groonga\-3.0.8> cmake \-\-build . \-\-config Release
+groonga\-3.0.9> cmake \-\-build . \-\-config Release
 .ft P
 .fi
 .UNINDENT
@@ -263,7 +255,7 @@ Install:
 .sp
 .nf
 .ft C
-groonga\-3.0.8> cmake \-\-build . \-\-config Release \-\-target Install
+groonga\-3.0.9> cmake \-\-build . \-\-config Release \-\-target Install
 .ft P
 .fi
 .UNINDENT
@@ -317,9 +309,9 @@ Download source:
 .sp
 .nf
 .ft C
-% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -719,9 +711,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -1173,6 +1165,83 @@ Install groonga\-normalizer\-mysql package:
 .fi
 .UNINDENT
 .UNINDENT
+.SS 13.10 Saucy Salamander
+.sp
+Add the Groonga apt repository.
+.sp
+/etc/apt/sources.list.d/groonga.list:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+deb http://packages.groonga.org/ubuntu/ saucy universe
+deb\-src http://packages.groonga.org/ubuntu/ saucy universe
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Install:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo apt\-get update
+% sudo apt\-get \-y \-\-allow\-unauthenticated install groonga\-keyring
+% sudo apt\-get update
+% sudo apt\-get \-y install groonga
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If you want to use \fI\%MeCab\fP as a
+tokenizer, install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
+Groonga status by Munin, install groonga\-munin\-plugins package.
+.sp
+Install groonga\-munin\-plugins package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-munin\-plugins
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+There is a package that provides MySQL compatible normalizer as
+Groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .SS Build from source
 .sp
 Install required packages to build groonga:
@@ -1193,9 +1262,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -1533,9 +1602,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -1740,9 +1809,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -1807,9 +1876,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% gtar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% gtar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 .ft P
 .fi
 .UNINDENT
@@ -1949,9 +2018,9 @@ steps:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.0.8.tar.gz
-% tar xvzf groonga\-3.0.8.tar.gz
-% cd groonga\-3.0.8
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.9.tar.gz
+% tar xvzf groonga\-3.0.9.tar.gz
+% cd groonga\-3.0.9
 % ./configure
 % make
 % sudo make install
@@ -2087,6 +2156,15 @@ Here is an example that enables column value compression by zlib:
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+The disabled reason is that memory leak occurs when it refers column value.
+This is already known issue as \fI\%GitHub#6\fP.
+This issue is not nothing to do with updating column value.
+.UNINDENT
+.UNINDENT
 .SS \fB\-\-with\-lzo\fP
 .sp
 Enables column value compression by LZO.
@@ -2104,6 +2182,15 @@ Here is an example that enables column value compression by LZO:
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+The disabled reason is that memory leak occurs when it refers column value.
+This is already known issue as \fI\%GitHub#6\fP.
+This issue is not nothing to do with updating column value.
+.UNINDENT
+.UNINDENT
 .SS \fB\-\-with\-message\-pack=MESSAGE_PACK_INSTALL_PREFIX\fP
 .sp
 Specifies where MessagePack is installed. If MessagePack isn\(aqt
@@ -8056,6 +8143,8 @@ katakana or hiragana. It\(aqs useful for searching in Japanese.
 For example, there is a registered word "日本". And "ニホン"
 (it must be katakana) is registered as its reading. An user
 can find "日本" by "ni", "二" or "に".
+.sp
+If you create dataset which is named as example by \fB/reference/executables/groonga\-suggest\-create\-dataset\fP command, you can update pairs of registered word and its reading by loading data to \(aq_key\(aq and \(aqkana\(aq column of item_example table explicitly for prefix RK search.
 .SS Cooccurrence search
 .sp
 Cooccurrence search can find registered words from user\(aqs
@@ -8367,121 +8456,47 @@ load \-\-table event_query \-\-each \(aqsuggest_preparer(_id, type, item, sequen
 .fi
 .UNINDENT
 .UNINDENT
-.SS Correction
+.SS How to update RK reading data
 .sp
-This section describes about the following correction
-features:
-.INDENT 0.0
-.IP \(bu 2
-How it works
-.IP \(bu 2
-How to use
-.IP \(bu 2
-How to learn
-.UNINDENT
-.SS How it works
+Groonga requires registered word and its reading for RK search, so load such data in the advance.
 .sp
-The correction feature uses three searches to compute corrected
-words:
+Here is the example to register "日本" which means Japanese in english.
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
-.INDENT 0.0
-.IP 1. 3
-Cooccurrence search against learned data.
-.IP 2. 3
-Similar search against registered words. (optional)
-.UNINDENT
+.sp
+.nf
+.ft C
+load \-\-table event_query \-\-each \(aqsuggest_preparer(_id, type, item, sequence, time, pair_query)\(aq
+[
+{"sequence": "1", "time": 1312950805.86058, "item": "日本", "type": "submit"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
-.SS Cooccurrence search
-.sp
-Cooccurrence search can find registered words from user\(aqs
-wrong input. It uses user submit sequences that will be
-learned from query logs, access logs and so on.
 .sp
-For example, there are the following user submissions:
-.TS
-center;
-|l|l|.
-_
-T{
-query
-T}	T{
-time
-T}
-_
-T{
-serach (typo!)
-T}	T{
-2011\-08\-10T22:20:50+09:00
-T}
-_
-T{
-search (fixed!)
-T}	T{
-2011\-08\-10T22:20:52+09:00
-T}
-_
-.TE
-.sp
-Groonga creates the following correction pair from the above
-submissions:
-.TS
-center;
-|l|l|.
-_
-T{
-input
-T}	T{
-corrected word
-T}
-_
-T{
-serach
-T}	T{
-search
-T}
-_
-.TE
-.sp
-Groonga treats continuous submissions within a minute as
-input correction by user. Not submitted user input sequence
-between two submissions isn\(aqt used as learned data for
-correction.
-.sp
-If an user inputs "serach" and cooccurrence search returns
-"search" because "serach" is in input column and
-corresponding corrected word column value is "search".
-.SS Similar search
-.sp
-Similar search can find registered words that has one or
-more the same tokens as user input. TokenBigram tokenizer is
-used for tokenization because suggest dataset schema
-created by \fB/reference/executables/groonga\-suggest\-create\-dataset\fP
-uses TokenBigram tokenizer as the default tokenizer.
-.sp
-For example, there is a registered query "search engine". An
-user can find "search engine" by "web search service",
-"sound engine" and so on. Because "search engine" and "web
-search engine" have the same token "search" and "search
-engine" and "sound engine" have the same token "engine".
+Here is the example to update RK data to complete "日本".
 .sp
-"search engine" is tokenized to "search" and "engine"
-tokens. (Groonga\(aqs TokenBigram tokenizer doesn\(aqt tokenize
-two characters for continuous alphabets and continuous
-digits for reducing search
-noise. TokenBigramSplitSymbolAlphaDigit tokenizer should be
-used to ensure tokenizing to two characters.) "web search
-service" is tokenized to "web", "search" and
-"service". "sound engine" is tokenized to "sound" and
-"engine".
-.SS How to use
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
 .sp
-Groonga provides \fB/reference/commands/suggest\fP command to use
-correction. \fI\-\-type correct\fP option requests corrections.
+.nf
+.ft C
+load \-\-table item_query
+[
+{"_key":"日本", "kana":["ニホン", "ニッポン"]}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .sp
-For example, here is an command to get correction results by
-"saerch":
+Then you can complete registered word "日本" by RK input \- "nihon".
 .sp
 Execution example:
 .INDENT 0.0
@@ -8489,7 +8504,7 @@ Execution example:
 .sp
 .nf
 .ft C
-suggest \-\-table item_query \-\-column kana \-\-types correction \-\-frequency_threshold 1 \-\-query saerch
+suggest \-\-table item_query \-\-column kana \-\-types complete \-\-frequency_threshold 1 \-\-query nihon
 # [
 #   [
 #     0,
@@ -8497,7 +8512,7 @@ suggest \-\-table item_query \-\-column kana \-\-types correction \-\-frequency_
 #     0.000355720520019531
 #   ],
 #   {
-#     "correct": [
+#     "complete": [
 #       [
 #         1
 #       ],
@@ -8512,8 +8527,8 @@ suggest \-\-table item_query \-\-column kana \-\-types correction \-\-frequency_
 #         ]
 #       ],
 #       [
-#         "search",
-#         1
+#         "日本",
+#         2
 #       ]
 #     ]
 #   }
@@ -8522,37 +8537,346 @@ suggest \-\-table item_query \-\-column kana \-\-types correction \-\-frequency_
 .fi
 .UNINDENT
 .UNINDENT
-.SS How it learns
 .sp
-Cooccurrence search uses learned data. They are based on
-query logs, access logs and so on. To create learned data,
-groonga needs user submit inputs with time stamp.
+Without loading above RK data, you can\(aqt complete registered word "日本" by query \- "nihon".
 .sp
-For example, an user wants to search by "search" but the
-user has typo "saerch" before inputs the correct query. The
-user inputs the query with the following sequence:
+As the column type of item_query table is VECTOR_COLUMN, you can register multiple readings for registered word.
+.sp
+This is the reason that you can also complete the registered word "日本" by query \- "nippon".
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
-.INDENT 0.0
-.IP 1. 3
-2011\-08\-10T13:33:23+09:00: s
-.IP 2. 3
-2011\-08\-10T13:33:23+09:00: sa
-.IP 3. 3
-2011\-08\-10T13:33:24+09:00: sae
-.IP 4. 3
-2011\-08\-10T13:33:24+09:00: saer
-.IP 5. 3
-2011\-08\-10T13:33:24+09:00: saerc
-.IP 6. 3
-2011\-08\-10T13:33:25+09:00: saerch (submit!)
-.IP 7. 3
-2011\-08\-10T13:33:29+09:00: serch (correcting...)
-.IP 8. 3
-2011\-08\-10T13:33:30+09:00: search (submit!)
-.UNINDENT
-.UNINDENT
-.UNINDENT
+.sp
+.nf
+.ft C
+suggest \-\-table item_query \-\-column kana \-\-types complete \-\-frequency_threshold 1 \-\-query nippon
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "complete": [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "日本",
+#         2
+#       ]
+#     ]
+#   }
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+This feature is very convenient because you can search registered word even though Japanese IM is disabled.
+.sp
+If there are multiple candidates as completed result, you can customize priority to set the value of "boost" column in item_query table.
+.sp
+Here is the example to customize priority for RK search.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+load \-\-table event_query \-\-each \(aqsuggest_preparer(_id, type, item, sequence, time, pair_query)\(aq
+[
+{"sequence": "1", "time": 1312950805.86059, "item": "日本語", "type": "submit"}
+{"sequence": "1", "time": 1312950805.86060, "item": "日本人", "type": "submit"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 2]
+load \-\-table item_query
+[
+{"_key":"日本語", "kana":"ニホンゴ"}
+{"_key":"日本人", "kana":"ニホンジン"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 2]
+suggest \-\-table item_query \-\-column kana \-\-types complete \-\-frequency_threshold 1 \-\-query nihon
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "complete": [
+#       [
+#         3
+#       ],
+#       [
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "日本",
+#         2
+#       ],
+#       [
+#         "日本人",
+#         2
+#       ],
+#       [
+#         "日本語",
+#         2
+#       ]
+#     ]
+#   }
+# ]
+load \-\-table item_query
+[
+{"_key":"日本人", "boost": 100},
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+suggest \-\-table item_query \-\-column kana \-\-types complete \-\-frequency_threshold 1 \-\-query nihon
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "complete": [
+#       [
+#         3
+#       ],
+#       [
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "日本人",
+#         102
+#       ],
+#       [
+#         "日本",
+#         2
+#       ],
+#       [
+#         "日本語",
+#         2
+#       ]
+#     ]
+#   }
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Correction
+.sp
+This section describes about the following correction
+features:
+.INDENT 0.0
+.IP \(bu 2
+How it works
+.IP \(bu 2
+How to use
+.IP \(bu 2
+How to learn
+.UNINDENT
+.SS How it works
+.sp
+The correction feature uses three searches to compute corrected
+words:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP 1. 3
+Cooccurrence search against learned data.
+.IP 2. 3
+Similar search against registered words. (optional)
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Cooccurrence search
+.sp
+Cooccurrence search can find registered words from user\(aqs
+wrong input. It uses user submit sequences that will be
+learned from query logs, access logs and so on.
+.sp
+For example, there are the following user submissions:
+.TS
+center;
+|l|l|.
+_
+T{
+query
+T}	T{
+time
+T}
+_
+T{
+serach (typo!)
+T}	T{
+2011\-08\-10T22:20:50+09:00
+T}
+_
+T{
+search (fixed!)
+T}	T{
+2011\-08\-10T22:20:52+09:00
+T}
+_
+.TE
+.sp
+Groonga creates the following correction pair from the above
+submissions:
+.TS
+center;
+|l|l|.
+_
+T{
+input
+T}	T{
+corrected word
+T}
+_
+T{
+serach
+T}	T{
+search
+T}
+_
+.TE
+.sp
+Groonga treats continuous submissions within a minute as
+input correction by user. Not submitted user input sequence
+between two submissions isn\(aqt used as learned data for
+correction.
+.sp
+If an user inputs "serach" and cooccurrence search returns
+"search" because "serach" is in input column and
+corresponding corrected word column value is "search".
+.SS Similar search
+.sp
+Similar search can find registered words that has one or
+more the same tokens as user input. TokenBigram tokenizer is
+used for tokenization because suggest dataset schema
+created by \fB/reference/executables/groonga\-suggest\-create\-dataset\fP
+uses TokenBigram tokenizer as the default tokenizer.
+.sp
+For example, there is a registered query "search engine". An
+user can find "search engine" by "web search service",
+"sound engine" and so on. Because "search engine" and "web
+search engine" have the same token "search" and "search
+engine" and "sound engine" have the same token "engine".
+.sp
+"search engine" is tokenized to "search" and "engine"
+tokens. (Groonga\(aqs TokenBigram tokenizer doesn\(aqt tokenize
+two characters for continuous alphabets and continuous
+digits for reducing search
+noise. TokenBigramSplitSymbolAlphaDigit tokenizer should be
+used to ensure tokenizing to two characters.) "web search
+service" is tokenized to "web", "search" and
+"service". "sound engine" is tokenized to "sound" and
+"engine".
+.SS How to use
+.sp
+Groonga provides \fB/reference/commands/suggest\fP command to use
+correction. \fI\-\-type correct\fP option requests corrections.
+.sp
+For example, here is an command to get correction results by
+"saerch":
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+suggest \-\-table item_query \-\-column kana \-\-types correction \-\-frequency_threshold 1 \-\-query saerch
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "correct": [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "search",
+#         1
+#       ]
+#     ]
+#   }
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS How it learns
+.sp
+Cooccurrence search uses learned data. They are based on
+query logs, access logs and so on. To create learned data,
+groonga needs user submit inputs with time stamp.
+.sp
+For example, an user wants to search by "search" but the
+user has typo "saerch" before inputs the correct query. The
+user inputs the query with the following sequence:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP 1. 3
+2011\-08\-10T13:33:23+09:00: s
+.IP 2. 3
+2011\-08\-10T13:33:23+09:00: sa
+.IP 3. 3
+2011\-08\-10T13:33:24+09:00: sae
+.IP 4. 3
+2011\-08\-10T13:33:24+09:00: saer
+.IP 5. 3
+2011\-08\-10T13:33:24+09:00: saerc
+.IP 6. 3
+2011\-08\-10T13:33:25+09:00: saerch (submit!)
+.IP 7. 3
+2011\-08\-10T13:33:29+09:00: serch (correcting...)
+.IP 8. 3
+2011\-08\-10T13:33:30+09:00: search (submit!)
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .sp
 Groonga can be learned from the input sequence by the
 following command:
@@ -10368,9 +10692,6 @@ DBに定義されているテーブルを削除します。
 .B \fBcolumn_remove\fP
 テーブルに定義されているカラムを削除します。
 .TP
-.B \fBview_add\fP
-VIEW型のテーブルに要素となるテーブルを定義します。
-.TP
 .B \fBload\fP
 テーブルにレコードを挿入します。
 .TP
@@ -10641,7 +10962,31 @@ Synopsis:
 .sp
 .nf
 .ft C
-groonga_database /path/to/groonga/database;
+groonga_database /path/to/groonga/database;
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B Default
+\fBgroonga_database /usr/local/var/lib/groonga/db/db;\fP
+.TP
+.B Context
+\fBhttp\fP, \fBserver\fP, \fBlocation\fP
+.UNINDENT
+.sp
+Specifies the path to a groonga database. This is the required
+directive.
+.SS \fBgroonga_database_auto_create\fP
+.sp
+Synopsis:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+groonga_database_auto_create on | off;
 .ft P
 .fi
 .UNINDENT
@@ -10649,17 +10994,23 @@ groonga_database /path/to/groonga/database;
 .INDENT 0.0
 .TP
 .B Default
-\fBgroonga_database /usr/local/var/lib/groonga/db/db;\fP
+\fBgroonga_database_auto_create on;\fP
 .TP
 .B Context
 \fBhttp\fP, \fBserver\fP, \fBlocation\fP
 .UNINDENT
 .sp
-Specifies the path to a groonga database. This is the required
-directive.
-.SS \fBgroonga_database_auto_create\fP
+Specifies whether groonga database is created automatically or not. If
+the value is \fBon\fP and the groonga database specified by
+\fIgroonga\-database\fP doesn\(aqt exist, the groonga database is created
+automatically. If the groonga database exists, groonga\-httpd does
+nothing.
 .sp
-TODO
+If parent directory doesn\(aqt exist, parent directory is also created
+recursively.
+.sp
+The default value is \fBon\fP. Normally, the value doesn\(aqt need to be
+changed.
 .SS \fBgroonga_base_path\fP
 .sp
 Synopsis:
@@ -10879,6 +11230,49 @@ This isn\(aqt a groonga\-httpd specific directive, but an nginx\(aqs one. For de
 see \fI\%http://wiki.nginx.org/CoreModule#worker_processes\fP.
 .sp
 By default, this is set to 1. It is nginx\(aqs default.
+.SS \fBgroonga_cache_limit\fP
+.sp
+This directive is introduced to customize cache limit for each worker process.
+.sp
+Synopsis:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+groonga_cache_limit CACHE_LIMIT;
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B Default
+100
+.TP
+.B Context
+\fBhttp\fP, \fBserver\fP, \fBlocation\fP
+.UNINDENT
+.sp
+Specifies groonga\(aqs limit of query cache in the \fBhttp\fP, \fBserver\fP or
+\fBlocation\fP block. The default value is 100.
+You can disable query cache to specify 0 to \fBgroonga_cache_limit\fP explicitly.
+.sp
+Examples:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+location /d/ {
+  groonga on;
+  # You can customize query cache limit for groonga.
+  groonga_cache_limit 100;
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .SS \fBproxy_cache\fP
 .sp
 In short, you can use nginx\(aqs reverse proxy and cache mechanism
@@ -11130,6 +11524,28 @@ groonga\-suggest\-create\-dataset [options] DATABASE DATASET
 .SS DESCTIPION
 .sp
 groonga\-suggest\-create\-dataset creates a dataset for \fB/suggest\fP. A database has many datasets. This command just defines schema for a suggestion dataset.
+.sp
+This command generates some tables and columns for \fB/suggest\fP.
+.sp
+Here is the list of such tables. If you specify \(aqquery\(aq as dataset name, following \(aq_DATASET\(aq suffix are replaced. Thus, \(aqitem_query\(aq, \(aqpair_query\(aq, \(aqsequence_query\(aq, \(aqevent_query\(aq tables are generated.
+.INDENT 0.0
+.IP \(bu 2
+event_type
+.IP \(bu 2
+bigram
+.IP \(bu 2
+kana
+.IP \(bu 2
+item_DATASET
+.IP \(bu 2
+pair_DATASET
+.IP \(bu 2
+sequence_DATASET
+.IP \(bu 2
+event_DATASET
+.IP \(bu 2
+configuration
+.UNINDENT
 .SS OPTIONS
 .sp
 None.
@@ -11145,8 +11561,100 @@ TODO
 .SS SEE ALSO
 .sp
 \fB/suggest\fP
-.. : doc:\fIgroonga\-suggest\-httpd\fP
-.. : doc:\fIgroonga\-suggest\-learner\fP
+\fBgroonga\-suggest\-httpd\fP
+\fBgroonga\-suggest\-learner\fP
+.SS groonga\-suggest\-httpd
+.SS Summary
+.sp
+TODO
+.SS Synopsis
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+groonga\-suggest\-httpd [options] database_path
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+TODO
+.SS Options
+.INDENT 0.0
+.TP
+.B \-p, \-\-port
+Specify http server port number. The default value is 8080.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-t, \-\-n\-threads
+Specify number of threads. The default value is 8.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-s, \-\-send\-endpoint
+Specify endpoint for sender.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-r, \-\-receive\-endpoint
+Specify endpoint for receiver.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-l, \-\-log\-base\-path
+Specify path prefix of log.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-n\-lines\-per\-log\-file
+Specify the number of lines in a log file. The default value is 1,000,000.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-d, \-\-daemon
+Specify this option to daemonize.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-disable\-max\-fd\-check
+Specify this option to disable checking max fd on start.
+.UNINDENT
+.SS Parameters
+.sp
+There is one required parameter \- \fBdatabase_path\fP.
+.SS \fBdatabase_path\fP
+.sp
+Specifies the path to a groonga database.
+.SS groonga\-suggest\-learner
+.SS Summary
+.sp
+TODO
+.SS Synopsis
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+groonga\-suggest\-learner [options] database_path
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+TODO
+.SS Options
+.sp
+TODO
+.SS Parameters
+.sp
+There is one required parameter \- \fBdatabase_path\fP.
+.SS \fBdatabase_path\fP
+.sp
+Specifies the path to a groonga database.
 .SS Output
 .sp
 Groonga supports the following output format types:
@@ -12022,7 +12530,7 @@ max number of query cache entries.
 .sp
 .nf
 .ft C
-[[HEADER, n_entries]]
+[[HEADER, N_ENTRIES]]
 .ft P
 .fi
 .UNINDENT
@@ -12035,10 +12543,10 @@ See \fB/reference/command/output_format\fP about \fBHEADER\fP.
 .UNINDENT
 .UNINDENT
 .sp
-\fBn_entries\fP
+\fBN_ENTRIES\fP
 .INDENT 0.0
 .INDENT 3.5
-\fBn_entries\fP is the current max number of query cache entries. It
+\fBN_ENTRIES\fP is the current max number of query cache entries. It
 is a number.
 .UNINDENT
 .UNINDENT
@@ -12363,11 +12871,15 @@ clearlock Entry.body
 .SS 関連項目
 .sp
 \fBload\fP
-.SS column_create
-.SS 名前
+.SS \fBcolumn_create\fP
+.SS Summary
 .sp
 column_create \- カラムの追加
-.SS 書式
+.sp
+groonga組込コマンドの一つであるcolumn_createについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+.sp
+column_createは、使用しているデータベースのテーブルに対してカラムを追加します。
+.SS Syntax
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -12378,12 +12890,34 @@ column_create table name flags type [source]
 .fi
 .UNINDENT
 .UNINDENT
-.SS 説明
+.SS Usage
 .sp
-groonga組込コマンドの一つであるcolumn_createについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+テーブルEntryに、ShortText型の値を格納するカラム、bodyを作成します。:
+.INDENT 0.0
+.INDENT 3.5
 .sp
-column_createは、使用しているデータベースのテーブルに対してカラムを追加します。
-.SS 引数
+.nf
+.ft C
+column_create Entry body \-\-type ShortText
+[true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+テーブルTermに、Entryテーブルのbodyカラムの値を対象とする完全転置インデックス型カラム、entry_bodyを作成します。:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+column_create Term entry_body COLUMN_INDEX|WITH_POSITION Entry body
+[true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
 .sp
 \fBtable\fP
 .INDENT 0.0
@@ -12417,6 +12951,16 @@ column_createは、使用しているデータベースのテーブルに対し
 インデックス型のカラムを作成します。
 .UNINDENT
 .sp
+There are two flags to compress the value of column, but you can\(aqt specify these flags for now because there are memory leaks issue \fI\%GitHub#6\fP when refers the value of column. This issue occurs both of them (zlib and lzo).
+.INDENT 0.0
+.TP
+.B 16, \fBCOMPRESS_ZLIB\fP
+Reserved. Compress the value of column by using zlib. This flag is disabled feature even if you build groonga with \fB\-\-with\-zlib\fP.
+.TP
+.B 32, \fBCOMPRESS_LZO\fP
+Reserved. Compress the value of column by using lzo. This flag is disabled feature even if you build groonga with \fB\-\-with\-lzo\fP.
+.UNINDENT
+.sp
 インデックス型のカラムについては、flagsの値に以下の値を加えることによって、追加の属
 性を指定することができます。
 .INDENT 0.0
@@ -12446,50 +12990,30 @@ column_createは、使用しているデータベースのテーブルに対し
 インデックス型のカラムを作成した場合は、インデックス対象となるカラムをsource引数に指定します。
 .UNINDENT
 .UNINDENT
-.SS 返値
-.SS json形式
+.SS Return value
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[成功かどうかのフラグ]
+[HEADER, SUCCEEDED]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fB成功かどうかのフラグ\fP
-.INDENT 0.0
-.INDENT 3.5
-エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
-.UNINDENT
-.UNINDENT
-.SS 例
-.sp
-テーブルEntryに、ShortText型の値を格納するカラム、bodyを作成します。:
+\fBHEADER\fP
 .INDENT 0.0
 .INDENT 3.5
-.sp
-.nf
-.ft C
-column_create Entry body \-\-type ShortText
-[true]
-.ft P
-.fi
+The format of HEADER is [0, UNIX_TIME_WHEN_COMMAND_IS_STARTED, ELAPSED_TIME].
+See \fB/reference/command/output_format\fP about HEADER.
 .UNINDENT
 .UNINDENT
 .sp
-テーブルTermに、Entryテーブルのbodyカラムの値を対象とする完全転置インデックス型カラム、entry_bodyを作成します。:
+\fBSUCCEEDED\fP
 .INDENT 0.0
 .INDENT 3.5
-.sp
-.nf
-.ft C
-column_create Term entry_body COLUMN_INDEX|WITH_POSITION Entry body
-[true]
-.ft P
-.fi
+If command is succeeded, it returns true on success, false otherwise.
 .UNINDENT
 .UNINDENT
 .SS column_list
@@ -13872,14 +14396,16 @@ There is no need to create table to use \fBnormalize\fP command.
 It is usefull for you to check the results of normalizer.
 .SS Syntax
 .sp
-\fBnormalize\fP commands takes two parameters \- \fBnormalizer\fP and \fBstring\fP.
-Both of them are required.
+\fBnormalize\fP commands has two required parameters. They are
+\fBnormalizer\fP and \fBstring\fP.
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-normalize normalizer string
+normalize normalizer
+          string
+          [flags=NONE]
 .ft P
 .fi
 .UNINDENT
@@ -13918,19 +14444,98 @@ This section describes parameters of \fBnormalizer\fP.
 There are required parameters, \fBnormalizer\fP and \fBstring\fP.
 .SS \fBnormalizer\fP
 .sp
-It specifies the name of normalizer.
-Currently, \fBnormalize\fP command accepts \fBNormalizerAuto\fP or \fBNormalizerNFKC51\fP as built\-in normalizer.
-If you want to try another normalizer, you need to register additional normalizer plugin by \fBregister\fP command.
+It specifies the normalizer name. \fBnormalize\fP command uses the
+normalizer that is named \fBnormalizer\fP.
+.sp
+See \fB/reference/normalizers\fP about built\-in normalizers.
+.sp
+Here is an example to use built\-in \fBNormalizerAuto\fP normalizer.
+.sp
+TODO
+.sp
+If you want to use other normalizers, you need to register additional
+normalizer plugin by \fBregister\fP command. For example, you can use
+MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP.
 .SS \fBstring\fP
 .sp
 It specifies any string which you want to normalize.
+.sp
+If you want to include spaces in \fBstring\fP, you need to quote
+\fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
+.sp
+Here is an example to use spaces in \fBstring\fP.
+.sp
+TODO
+.SS Optional parameters
+.sp
+There are optional parameters.
+.SS \fBflags\fP
+.sp
+It specifies a normalization customize options. You can specify
+multiple options separated by "\fB|\fP". For example,
+\fBREMOVE_BLANK|WITH_TYPES\fP.
+.sp
+Here are available flags.
+.TS
+center;
+|l|l|.
+_
+T{
+Flag
+T}	T{
+Description
+T}
+_
+T{
+\fBNONE\fP
+T}	T{
+Just ignored.
+T}
+_
+T{
+\fBREMOVE_BLANK\fP
+T}	T{
+TODO
+T}
+_
+T{
+\fBWITH_TYPES\fP
+T}	T{
+TODO
+T}
+_
+T{
+\fBWITH_CHECKS\fP
+T}	T{
+TODO
+T}
+_
+T{
+\fBREMOVE_TOKENIZED_DELIMITER\fP
+T}	T{
+TODO
+T}
+_
+.TE
+.sp
+Here is an example that uses \fBREMOVE_BLANK\fP.
+.sp
+TODO
+.sp
+Here is an example that uses \fBWITH_TYPES\fP.
+.sp
+TODO
+.sp
+Here is an example that uses \fBREMOVE_TOKENIZED_DELIMITER\fP.
+.sp
+TODO
 .SS Return value
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, normalized]
+[HEADER, normalized_text]
 .ft P
 .fi
 .UNINDENT
@@ -13944,10 +14549,34 @@ See \fB/reference/command/output_format\fP about HEADER.
 .UNINDENT
 .UNINDENT
 .sp
-\fBnormalized\fP
+\fBnormalized_text\fP
 .INDENT 0.0
 .INDENT 3.5
-normalized is the normalized text by the specified normalizer.
+\fBnormalized_text\fP is an object that has the following attributes.
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBnormalized\fP
+T}	T{
+The normalized text.
+T}
+_
+T{
+\fBtypes\fP
+T}	T{
+An array of types of the normalized text. The N\-th \fBtypes\fP shows
+the type of the N\-th character in \fBnormalized\fP.
+T}
+_
+.TE
 .UNINDENT
 .UNINDENT
 .SS See also
@@ -14066,7 +14695,7 @@ See \fB/reference/command/output_format\fP for \fBHEADER\fP.
 .SS \fBruby_eval\fP
 .SS Summary
 .sp
-\fBruby_eval\fP command evaluates ruby script and returns the result.
+\fBruby_eval\fP command evaluates Ruby script and returns the result.
 .SS Syntax
 .sp
 \fBruby_eval\fP has one required parameter:
@@ -14075,7 +14704,7 @@ See \fB/reference/command/output_format\fP for \fBHEADER\fP.
 .sp
 .nf
 .ft C
-ruby_eval ruby_script
+ruby_eval script
 .ft P
 .fi
 .UNINDENT
@@ -14084,7 +14713,7 @@ ruby_eval ruby_script
 .sp
 You can execute any scripts which mruby supports by calling \fBruby_eval\fP.
 .sp
-Here is an example that just calculate \fB1 + 2\fP by mruby plugin.
+Here is an example that just calculate \fB1 + 2\fP as Ruby script.
 .sp
 Execution example:
 .INDENT 0.0
@@ -14108,18 +14737,19 @@ and the specification may be changed in the future.
 .SS Parameters
 .sp
 This section describes all parameters.
-.SS \fBruby_script\fP
+.SS \fBscript\fP
 .sp
-It specifies the ruby script which you want to evaluate.
+It specifies the Ruby script which you want to evaluate.
 .SS Return value
 .sp
-\fBruby_eval\fP returns the evaluated result which key is "value" as json format:
+\fBruby_eval\fP returns the evaluated result with metadata such as
+exception information (Including metadata isn\(aqt implemented yet):
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[[HEADER, EVALUATED]]
+[HEADER, {"value": EVALUATED_VALUE}]
 .ft P
 .fi
 .UNINDENT
@@ -14132,36 +14762,82 @@ See \fB/reference/command/output_format\fP about \fBHEADER\fP.
 .UNINDENT
 .UNINDENT
 .sp
-\fBEVALUATED\fP
+\fBEVALUATED_VALUE\fP
 .INDENT 0.0
 .INDENT 3.5
-\fBEVALUATED\fP consists of pair of key and value in forms of {key:value}.
-.TS
-center;
-|l|l|.
-_
-T{
-Name
-T}	T{
-Description
-T}
-_
-T{
-\fBkey\fP
-T}	T{
-reserved word \(aqvalue\(aq.
-T}
-_
-T{
-\fBvalue\fP
-T}	T{
-the value of evaluated script. It must be a number.
-T}
-_
-.TE
+\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP.
+.sp
+\fBruby_eval\fP supports only a number for evaluated value for now.
+Supported types will be increased in the future.
+.UNINDENT
+.UNINDENT
+.SS See also
+.SS \fBruby_load\fP
+.SS Summary
+.sp
+\fBruby_load\fP command loads specified Ruby script.
+.SS Syntax
+.sp
+\fBruby_load\fP has one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+ruby_load path
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+You can load any script file which mruby supports by calling \fBruby_load\fP.
+.sp
+Here is an example that just load \fBexpression.rb\fP as Ruby script.
+.sp
+Register \fBruby/load\fP plugin to use \fBruby_load\fP command in advance.
+.sp
+Note that \fBruby_load\fP is implemented as an experimental plugin,
+and the specification may be changed in the future.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBpath\fP
+.sp
+It specifies the Ruby script path which you want to load.
+.SS Return value
+.sp
+\fBruby_load\fP returns the loaded result with metadata such as
+exception information (Including metadata isn\(aqt implemented yet):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, {"value": LOADED_VALUE}]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+See \fB/reference/command/output_format\fP about \fBHEADER\fP.
+.UNINDENT
+.UNINDENT
+.sp
+\fBLOADED_VALUE\fP
+.INDENT 0.0
+.INDENT 3.5
+\fBLOADED_VALUE\fP is the loaded value of ruby script.
+.sp
+\fBruby_load\fP just return \fBnull\fP as \fBLOADED_VALUE\fP for now, it will be supported in the future.
 .UNINDENT
 .UNINDENT
 .SS See also
+.sp
+\fB/reference/commands/ruby_eval\fP
 .SS \fBselect\fP
 .SS Summary
 .sp
@@ -18168,7 +18844,7 @@ tokenizer that is named \fBtokenizer\fP.
 .sp
 See \fB/reference/tokenizers\fP about built\-in tokenizers.
 .sp
-Here is an example to use \fBTokenTrigram\fP tokenizer.
+Here is an example to use built\-in \fBTokenTrigram\fP tokenizer.
 .sp
 Execution example:
 .INDENT 0.0
@@ -18253,12 +18929,14 @@ tokenize TokenTrigram "Fulltext Search"
 .sp
 If you want to use other tokenizers, you need to register additional
 tokenizer plugin by \fBregister\fP command. For example, you can use
-MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP.
+\fI\%KyTea\fP based tokenizer by
+registering \fBtokenizers/kytea\fP.
 .SS \fBstring\fP
 .sp
-It specifies any string which you want to tokenize. If you want to
-include spaces in \fBstring\fP, you need to quote \fBstring\fP by
-single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
+It specifies any string which you want to tokenize.
+.sp
+If you want to include spaces in \fBstring\fP, you need to quote
+\fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
 .sp
 Here is an example to use spaces in \fBstring\fP.
 .sp
@@ -26561,6 +27239,221 @@ Example:
 .fi
 .UNINDENT
 .UNINDENT
+.SS Tuning
+.SS Summary
+.sp
+There are some tuning parameters for improving groonga performance or
+handling a large database.
+.SS Parameters
+.sp
+This section describes parameters.
+.SS The max number of open files per process
+.sp
+This parameter is for handling a large database.
+.sp
+Groonga creates one or more files per table and colum. If your
+database has many tables and columns, groonga process needs to open
+many files.
+.sp
+System limits the max number of open files per process. So you need to
+relax the limitation.
+.sp
+Here is an expression that compute how many files are opened by
+groonga:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+3 (for DB) +
+  N tables +
+  N columns (except index clumns) +
+  (N index columns * 2) +
+  X (the number of plugins etc.)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example schema:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Entries TABLE_HASH_KEY ShortText
+column_create Entries content COLUMN_SCALAR Text
+column_create Entries n_likes COLUMN_SCALAR UInt32
+table_create Terms TABLE_PAT_KEY|KEY_NORMALIZE ShortText \-\-default_tokenizer TokenBigram
+column_create Terms entries_key_index COLUMN_INDEX|WITH_POSITION Entries _key
+column_create Terms entries_content_index COLUMN_INDEX|WITH_POSITION Entries content
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+This example opens at least 11 files:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+3 +
+  2 (Entries and Terms) +
+  2 (Entries.content and Entries.n_likes) +
+  4 (Terms.entries_key_index and Terms.entries_content_index) +
+  X = 11 + X
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Memory usage
+.sp
+This parameter is for handling a large database.
+.sp
+Groonga maps database files onto memory and accesses to them. Groonga
+doesn\(aqt maps unnecessary files onto memory until they are nneded.
+.sp
+If you access to all data in database, all database files are mapped
+onto memory.  If total size of your database files is 6GiB, your
+groonga process uses 6GiB memory.
+.sp
+Normally, your all database files aren\(aqt mapped onto memry. But is may
+be occurred. It is an example case that you dump your database.
+.sp
+You must have memory and swap that is larger than database.
+.SS Linux
+.sp
+This section describes how to configure parameters on Linux.
+.SS nofile
+.sp
+You can relax the \fItuning\-max\-n\-open\-files\fP parameter by creating
+a configuration file \fB/etc/security/limits.d/groonga.conf\fP that has
+the following content:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+${USER} soft nofile ${MAX_VALUE}
+${USER} hard nofile ${MAX_VALUE}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If you run \fBgroonga\fP process by \fBgroonga\fP user and your groonga
+process needs to open less than 10000 files, use the following
+configuration:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+groonga soft nofile 10000
+groonga hard nofile 10000
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The configuration is applied after your groonga service is restarted
+or re\-login as your groonga user.
+.SS vm.overcommit_memory
+.sp
+This is \fItuning\-memory\-usage\fP related parameter. You can handle a
+database that is larger than your memory and swap by setting
+\fBvm.overcommit_memory\fP kernel parameter to 1. 1 means that groonga
+can always map database files onto memory. It is no problem until
+groonga touch mapped database files that their size is larger than
+memory and swap. Groonga recommends the configuration.
+.sp
+See \fI\%Linux kernel documentaion about overcommit\fP
+about \fBvm.overcommit_memory\fP parameter details.
+.sp
+You can set the configuration by putting a configuration file
+\fB/etc/sysctl.d/groonga.conf\fP that has the following content:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+vm.overcommit_memory = 1
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The configuration can be applied by restarting your system or run the
+following command:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo sysctl \-p
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS vm.max_map_count
+.sp
+This is \fItuning\-memory\-usage\fP related parameter. You can handle a
+16GiB or more larger size database by increasing \fBvm.max_map_count\fP
+kernel parameter. The parameter limits the max number of memory maps.
+.sp
+The default value of the kernel parameter may be 65530 or 65536.
+Groonga maps 256KiB memory chunk at one time. If a database is larger
+than 16GiB, groonga reaches the limitation. (\fB256KiB * 65536 = 16GiB\fP)
+.sp
+You needs to increase the value of the kernel parameter to handle
+16GiB or more larger size database. For example, you can handle almost
+32GiB size database by \fB65536 * 2 = 131072\fP. You can set the
+configuration by putting a configuration file
+\fB/etc/sysctl.d/groonga.conf\fP that has the following content:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+vm.max_map_count = 131072
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Note that your real confiugration file will be the following because
+you already have \fBvm.overcommit_memory\fP configuration:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+vm.overcommit_memory = 1
+vm.max_map_count = 131072
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The configuration can be applied by restarting your system or run the
+following command:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% sudo sysctl \-p
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS FreeBSD
+.sp
+This section describes how to configure parameters on FreeBSD.
+.SS kern.maxfileperproc
+.sp
+TODO
 .SS API
 .sp
 Groonga can be used as a fulltext search library. This section
@@ -29788,6 +30681,56 @@ TokenBigramIgnoreBlankSplitSymbolAlphaDigit: 記号・アルファベット・
 .UNINDENT
 .sp
 この場合も対策方法1同様、検索ノイズが上位に現れる可能性が高くなることに注意してください。検索ノイズが多くなった場合は指定する値を低くする必要があります。
+.SS How to avoid mmap Cannot allocate memory error
+.SS Example
+.sp
+There is a case following mmap error in log file:
+.INDENT 0.0
+.INDENT 3.5
+2013\-06\-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot allocate memory <13036498944>
+.UNINDENT
+.UNINDENT
+.sp
+Note that <13036498944> means total size of mmap (almost 12GB) in this case.
+.SS Solution
+.sp
+So you need to confirm following point of views.
+.INDENT 0.0
+.IP \(bu 2
+Are there enough free memory?
+.IP \(bu 2
+Are maximum number of mappings exceeded?
+.UNINDENT
+.sp
+To check there are enough free memory, you can use vmstat command.
+.sp
+To check whether maximum number of mappings are exceeded, you can investigate the value of vm.max_map_count.
+.sp
+If this issue is fixed by modifying the value of vm.max_map_count, it\(aqs exactly the reason.
+.sp
+As groonga allocates memory chunks each 256KB, you can estimate the size of database you can handle by following formula:
+.INDENT 0.0
+.INDENT 3.5
+(database size) = vm.max_map_count * (memory chunks)
+.UNINDENT
+.UNINDENT
+.sp
+If you want to handle over 16GB groonga database, you must specify at least 65536 as the value of vm.max_map_count:
+.INDENT 0.0
+.INDENT 3.5
+database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)
+.UNINDENT
+.UNINDENT
+.sp
+You can modify vm.max_map_count temporary by sudo sysctl \-w vm.max_map_count=65536.
+.sp
+Then save the configuration value to /etc/sysctl.conf or /etc/sysctl.d/
+.nf
+*
+.fi
+.conf.
+.sp
+See \fB/reference/tuning\fP documentation about tuning related parameters.
 .SH DEVELOPMENT
 .sp
 This section describes about developing with groonga. You may develop
@@ -30052,6 +30995,9 @@ groongaのドキュメントは、Sphinxというツールを用いて作成さ
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+This document is also ditributed in forms of release source archive and updated time to time.
+If you want to refer latest documentation in source form, you can view such files via GitHub repository browser (\fI\%https://github.com/groonga/groonga/tree/master/doc/source\fP).
 .SS pdfの作成
 .sp
 groongaのドキュメントは、pdf出力することもできます。rst2pdfと、IPAフォント(IPA Gothic/IPAexGothic)が必要となります。