Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.4
-
None
Description
By the test case and the outcome, it looks like a slightly more complicated variation of the recently closed MDEV-29954 (Unique hash key on column prefix is computed incorrectly), so maybe there is still something to fix. Or maybe it's just one of endless unique hash errors, completely unrelated to MDEV-29954.
CREATE TABLE t (c VARCHAR(1024) UNIQUE) ENGINE=MyISAM WITH SYSTEM VERSIONING; |
INSERT INTO t (c) VALUES ('foo'); |
DELETE FROM t; |
CHECK TABLE t EXTENDED; |
 |
# Cleanup
|
DROP TABLE t; |
|
10.4 c9b0c006e0491c9f7a1dae07090db3cdb87da446 |
CHECK TABLE t EXTENDED;
|
Table Op Msg_type Msg_text
|
test.t check error Record at: 0 Can't find key for index: 1
|
test.t check error Corrupt
|
DROP TABLE t;
|
bug.thr2 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2024-03-09 19:22:12
|
line
|
2024-03-09 19:22:12 4 [ERROR] Got an error from thread_id=4, /data/bld/11.4-asan/storage/myisam/ha_myisam.cc:1142
|
2024-03-09 19:22:12 4 [ERROR] MariaDB thread id 4, OS thread handle 140187211245248, query id 25 localhost root Checking table
|
^ Found warnings in /mnt8t/bld/11.4-asan/mysql-test/var/log/mysqld.1.err
|
Attachments
Issue Links
- relates to
-
-
- Closed
-