Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.0.11-galera
-
None
-
None
-
Linux guest 3.2.43-grsec-sma #1 SMP Mon Jun 17 14:23:20 CEST 2013 x86_64 GNU/Linux
Description
Output of explain seems like not to use fulltext index:
mysql> DROP TABLE IF EXISTS `test`;
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
mysql> CREATE TABLE IF NOT EXISTS `test` (
|
-> `id` int(10) unsigned NOT NULL,
|
-> `kereses` mediumtext NOT NULL,
|
-> PRIMARY KEY(id),
|
-> FULLTEXT keres(kereses)
|
-> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPACT;
|
Query OK, 0 rows affected (0.03 sec)
|
|
|
mysql> explain select SQL_CALC_FOUND_ROWS id,match(kereses)against('+aaa +bbb'in boolean mode)relevance from test where match(kereses)against('+aaa +bbb'in boolean mode)order by relevance desc limit 0,20;
|
+------+-------------+-------+----------+---------------+-------+---------+------+------+----------------------------------------------+
|
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
|
+------+-------------+-------+----------+---------------+-------+---------+------+------+----------------------------------------------+
|
| 1 | SIMPLE | test | fulltext | keres | keres | 0 | | 1 | Using where; Using temporary; Using filesort |
|
+------+-------------+-------+----------+---------------+-------+---------+------+------+----------------------------------------------+
|
1 row in set (0.00 sec)
|
|
|
mysql>
|
Why Using temporary and using filesort in extra field? Is this good?