Bug #16489 utf8 + fulltext leads to corrupt index file.
Submitted: 13 Jan 2006 17:47 Modified: 26 Jan 2006 2:33
Reporter: Aleksey Kishkin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.1.17 OS:Linux (linux)
Assigned to: Sergey Vojtovich CPU Architecture:Any
Tags: corruption, myisam

[13 Jan 2006 17:47] Aleksey Kishkin 
Description:
after all patches from bug #5686 , bug #11336 and bug #13712  indexes still periodicaly corrupts. Every several days in the error log appears warnings about "key in wrong position at page..." 

tested against mysql 4.1.17 from bk tree

How to repeat:
in hidden part
[20 Jan 2006 11:35] Sergey Vojtovich 
I was able to repeat this bug and simplify a testcase.
Simplified testcase:
SET NAMES utf8;
CREATE TABLE t1(a TEXT, FULLTEXT(a)) COLLATE utf8_unicode_ci;
INSERT INTO t1 VALUES ('abб═c d');
UPDATE t1 SET a='ab c d';
UPDATE t1 SET a='abб═c';
CHECK TABLE t1;
DROP TABLE t1;

We're working on fix now.
[23 Jan 2006 13:15] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/1495
[23 Jan 2006 16:54] Sergey Vojtovich 
Fixed that UPDATE statement crashes multi-byte charset fulltext index.
Fixed in 4.1.18, 5.0.19.
[26 Jan 2006 2:33] Mike Hillyer 
Documented in 4.1.18 and 5.0.19 changelogs:

  <listitem>
        <para>
          <literal>UPDATE</literal> statement crashed multi-byte
          character set <literal>FULLTEXT</literal> index. (Bug #16489) 
        </para>
      </listitem>