Bug #6447 | set GLOBAL key_cache_block_size=2048; crashes fulltext indices | ||
---|---|---|---|
Submitted: | 5 Nov 2004 2:58 | Modified: | 17 Nov 2004 1:34 |
Reporter: | Mark Maunder | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 4.1.7-standard | OS: | Linux (Linux 2.6) |
Assigned to: | Igor Babaev | CPU Architecture: | Any |
Tags: | key_cache_block_size |
[5 Nov 2004 2:58]
Mark Maunder
[5 Nov 2004 3:03]
Mark Maunder
Sorry, forgot to mention, the first step when recreating this is: set GLOBAL key_cache_block_size=2048;
[5 Nov 2004 8:43]
MySQL Verification Team
Verified with 4.1.8-debug-log
[17 Nov 2004 1:34]
Igor Babaev
The bug could be reproduce with much simpler test (thanks to Sergei G). This test now is added to mysql-test/t/key_cache.test. ChangeSet 1.2108 04/11/16 13:58:49 igor@rurik.mysql.com +3 -0 key_cache.result, key_cache.test: Added a test case for bug #6447. mf_keycache.c: Fixed bug #6447. Erronious code in the key_cache_read function caused problems when reading key blocks with offset>0 into key cache. The code of key_cache_insert and key_cache_write was modified similarly.