Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
3858bf1f
Commit
3858bf1f
authored
Oct 03, 2002
by
serg@serg.mysql.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fixed typo: s/ft_max_word_len_sort/ft_max_word_len_for_sort/
parent
b5ea7e8e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
Docs/manual.texi
Docs/manual.texi
+3
-3
No files found.
Docs/manual.texi
View file @
3858bf1f
...
@@ -20039,15 +20039,15 @@ The maximum length of the word to be included in a @code{FULLTEXT} index.
...
@@ -20039,15 +20039,15 @@ The maximum length of the word to be included in a @code{FULLTEXT} index.
@strong{Note: @code{FULLTEXT} indexes must be rebuilt after changing
@strong{Note: @code{FULLTEXT} indexes must be rebuilt after changing
this variable.} (This option is new for MySQL 4.0.)
this variable.} (This option is new for MySQL 4.0.)
@item @code{ft_max_word_len_sort}
@item @code{ft_max_word_len_
for_
sort}
The maximum length of the word in a @code{FULLTEXT} index
The maximum length of the word in a @code{FULLTEXT} index
to be used in fast index recreation method in @code{REPAIR},
to be used in fast index recreation method in @code{REPAIR},
@code{CREATE INDEX}, or @code{ALTER TABLE}. Longer words are inserted the
@code{CREATE INDEX}, or @code{ALTER TABLE}. Longer words are inserted the
slow way. The rule of the thumb is as follows: with
slow way. The rule of the thumb is as follows: with
@code{ft_max_word_len_sort} increasing, @strong{MySQL} will create bigger
@code{ft_max_word_len_
for_
sort} increasing, @strong{MySQL} will create bigger
temporary files (thus slowing the process down, due to disk I/O), and will put
temporary files (thus slowing the process down, due to disk I/O), and will put
fewer keys in one sort block (again, decreasing the efficiency). When
fewer keys in one sort block (again, decreasing the efficiency). When
@code{ft_max_word_len_sort} is too small, instead, @strong{MySQL} will insert a
@code{ft_max_word_len_
for_
sort} is too small, instead, @strong{MySQL} will insert a
lot of words into index the slow way, but short words will be inserted very
lot of words into index the slow way, but short words will be inserted very
quickly.
quickly.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment