[MDEV-29954] Unique hash key on column prefix is computed incorrectly - Jira

XML

Word

Printable

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL)
Fix Version/s: 10.5.24, 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3
Component/s: Admin statements, Storage Engine - InnoDB
Labels:
- corruption
- regression

--source include/have_innodb.inc

CREATE TABLE t (a TINYBLOB, b CHAR(64), UNIQUE(a,b(8))) ENGINE=InnoDB;

INSERT INTO t VALUES ('foo','bar');

CHECK TABLE t EXTENDED;

# Cleanup

DROP TABLE t;

10.6 79dc3989f
CHECK TABLE t EXTENDED;
Table Op Msg_type Msg_text
test.t check Warning InnoDB: Index 'a' contains 0 entries, should be 1.
test.t check error Corrupt
DROP TABLE t;
bug.15430 'innodb' [ fail ] Found warnings/errors in server log file!
Test ended at 2022-11-06 14:15:27
line
2022-11-06 14:15:26 4 [ERROR] InnoDB: Flagged corruption of `a` in table `test`.`t` in CHECK TABLE; Wrong count

The error started showing up on 10.6 after

commit ab0190101b0587e0e03b2d75a967050b9a85fd1b (HEAD)

Author: Marko Mäkelä

Date:   Fri Oct 21 10:02:54 2022 +0300

    MDEV-24402: InnoDB CHECK TABLE ... EXTENDED

is blocked by

MDEV-27653 long uniques don't work with unicode collations

is caused by

MDEV-371 Unique indexes for blobs

relates to

MDEV-24402 CHECK TABLE may miss some cases of index inconsistencies

MDEV-33641 Unique hash key on a versioned MyISAM table leads to corruption errors

MDEV-33236 InnoDB: Flagged corruption, Assertion `inited==INDEX' failed

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.