Bug #31950 | repair table hangs while processing multicolumn utf8 fulltext index | ||
---|---|---|---|
Submitted: | 30 Oct 2007 14:28 | Modified: | 15 Nov 2007 15:31 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S2 (Serious) |
Version: | 5.0.50 | OS: | Any |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
Tags: | bfsm_2007_11_01, fulltext, hang |
[30 Oct 2007 14:28]
Shane Bester
[30 Oct 2007 14:35]
MySQL Verification Team
some debug info
Attachment: bug31950_debug_info.txt (text/plain), 4.56 KiB.
[1 Nov 2007 13:24]
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/36868 ChangeSet@1.2547, 2007-11-01 16:27:01+04:00, svoj@mysql.com +1 -0 BUG#31950 - repair table hangs while processing multicolumn utf8 fulltext index Having a table with broken multibyte characters may cause fulltext parser dead-loop. Since normally it is not possible to insert broken multibyte sequence into a table, this problem may arise only if table is damaged. Affected statements are: - CHECK/REPAIR against damaged table with fulltext index; - boolean mode phrase search against damaged table with or without fulltext inex; - boolean mode searches without index; - nlq searches. No test case for this fix. Affects 5.0 only.
[14 Nov 2007 9:41]
Bugs System
Pushed into 6.0.4-alpha
[14 Nov 2007 9:45]
Bugs System
Pushed into 5.1.23-rc
[14 Nov 2007 9:50]
Bugs System
Pushed into 5.0.52
[15 Nov 2007 15:31]
Paul DuBois
Noted in 5.0.52 changelog. A column with malformed multi-byte characters could cause the full-text parser to go into an infinite loop.