Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4, 10.5, 10.6, 10.7, 10.11, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5
Description
Similar to MDEV-26492, but with a different error (134 instead of 126), no key_buffer_size change, and --log-bin is required.
# mysqld options required for replay: --log-bin |
SET sql_mode=''; |
SET GLOBAL key_cache_segments=1; |
CREATE TEMPORARY TABLE t (f INT KEY) ENGINE=MyISAM; |
INSERT INTO t VALUES (1),(2),(3); |
LOAD INDEX INTO CACHE t INDEX (PRIMARY) IGNORE LEAVES; |
SELECT * FROM t LIMIT 5; |
INSERT INTO t VALUES (4),(5),(6),(7),(8),(9),(10),(11); # Note: ALL insert values required |
DELETE FROM t; |
INSERT INTO t VALUES (1); |
SET GLOBAL key_cache_segments=1; |
SELECT * FROM t; |
Leads to:
10.11.8 64314d3094ef5eb52223c613632292be96bd7732 (Optimized) |
10.11.8-opt>SELECT * FROM t;
|
ERROR 1032 (HY000): Can't find record in 't'
|
10.11.8-opt>
|
 |
2024-05-24 11:15:34 5 [ERROR] Got error 134 when reading table '/test/MD070524-mariadb-10.11.8-linux-x86_64-opt/data/#sql-temptable-1ef56e-5-0'
|
2024-05-24 11:15:34 5 [ERROR] mariadbd: Can't find record in 't'
|
|
Bug confirmed present in:
MariaDB: 10.4.34 (dbg), 10.4.34 (opt), 10.5.26 (dbg), 10.5.26 (opt), 10.6.18 (dbg), 10.6.18 (opt), 10.11.8 (dbg), 10.11.8 (opt), 11.0.6 (dbg), 11.0.6 (opt), 11.1.5 (dbg), 11.1.5 (opt), 11.2.4 (dbg), 11.2.4 (opt), 11.3.3 (dbg), 11.3.3 (opt), 11.4.2 (dbg), 11.4.2 (opt), 11.5.0 (dbg), 11.5.0 (opt)
$ ./bin/perror 134
|
MariaDB error code 134: Record was already deleted (or record file crashed)
|
Attachments
Issue Links
- relates to
-
MDEV-26492 Got error 126 / mysqld: Index for table 't' is corrupt (key_cache_segments variation), SIGSEGV in get_all_tables
-
- Confirmed
-