mysql-55-eb allows invalid per-index KEY_BLOCK_SIZE values
Bug #783393 reported by
Philip Stoev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
percona-projects-qa |
Fix Released
|
Medium
|
Alexey Kopytov |
Bug Description
Now that per-table KEY_BLOCK_SIZE has a meaning with HEAP tables, the engine should also handle or reject per-index KEY_BLOCK_SIZE. Right now, the following statement:
CREATE TABLE t1 (f1 VARCHAR(512), KEY (f1) KEY_BLOCK_SIZE=12) ENGINE=HEAP ROW_FORMAT=DYNAMIC KEY_BLOCK_
returns OK and KEY_BLOCK_SIZE=12 is preserved in SHOW CREATE TABLE even though it is too small to accomodate a VARCHAR(512) column.
If the same statement is issued against MyISAM, the value of KEY_BLOCK_SIZE will be automatically updated to a valid one.
Related branches
Changed in percona-projects-qa: | |
assignee: | nobody → Laurynas Biveinis (laurynas-biveinis) |
Changed in percona-projects-qa: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 5.5.13-eb |
Changed in percona-projects-qa: | |
assignee: | Laurynas Biveinis (laurynas-biveinis) → Alexey Kopytov (akopytov) |
status: | Triaged → In Progress |
Changed in percona-projects-qa: | |
status: | In Progress → Fix Committed |
Changed in percona-projects-qa: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.