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
349ecb09
Commit
349ecb09
authored
Aug 07, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
one more "suboptimal memory usage during REPAIR for FULLTEXT keys" bug fixed
parent
b31ae3dd
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
myisam/mi_check.c
myisam/mi_check.c
+6
-3
No files found.
myisam/mi_check.c
View file @
349ecb09
...
...
@@ -3671,12 +3671,15 @@ ha_checksum mi_byte_checksum(const byte *buf, uint length)
static
my_bool
mi_too_big_key_for_sort
(
MI_KEYDEF
*
key
,
ha_rows
rows
)
{
uint
key_maxlength
=
key
->
maxlength
;
if
(
key
->
flag
&
HA_FULLTEXT
)
key_maxlength
+=
ft_max_word_len_for_sort
-
HA_FT_MAXLEN
;
return
(
key
->
flag
&
(
HA_BINARY_PACK_KEY
|
HA_VAR_LENGTH_KEY
|
HA_FULLTEXT
)
&&
((
ulonglong
)
rows
*
key
->
maxlength
>
((
ulonglong
)
rows
*
key
_
maxlength
>
(
ulonglong
)
myisam_max_temp_length
||
(
ulonglong
)
rows
*
(
key
->
maxlength
-
key
->
minlength
)
/
2
>
(
ulonglong
)
rows
*
(
key
_
maxlength
-
key
->
minlength
)
/
2
>
myisam_max_extra_temp_length
||
(
rows
==
0
&&
(
key
->
maxlength
/
key
->
minlength
)
>
2
)));
(
rows
==
0
&&
(
key
_
maxlength
/
key
->
minlength
)
>
2
)));
}
...
...
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