| Bug #8609 | load index into cache fails with fulltext and other character index | ||
|---|---|---|---|
| Submitted: | 18 Feb 2005 21:00 | Modified: | 19 Feb 2005 8:05 |
| Reporter: | Braxton Robbason | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
| Version: | MySQL 5.0.2 alpha | OS: | Linux (fedora core 3) |
| Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[19 Feb 2005 8:05]
Sergei Golubchik
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
It was fixed in 4.1.8 (and 5.0.3)
Description: load index into cache tablename fails when there is a fulltext index and a standard index on a varchar column of the same table. It should be easy to reproduce. How to repeat: <pre> mysql> create table foobar(col1 int not null auto_increment primary key, -> col2 varchar(255), col3 text, index cdex(col2), fulltext index wdex (col3)); Query OK, 0 rows affected (0.01 sec) mysql> mysql> insert into foobar(col2,col3) values ('hello','world'); Query OK, 1 row affected (0.00 sec) mysql> mysql> LOAD INDEX INTO CACHE foobar; +--------------+--------------+----------+-----------------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+--------------+----------+-----------------------------------+ | crawl.foobar | preload_keys | error | Indexes use different block sizes | | crawl.foobar | preload_keys | status | Operation failed | +--------------+--------------+----------+-----------------------------------+ </pre>