Details
-
Bug
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.11, 11.4, 11.8, 12.3, 10.6.23
-
Can result in unexpected behaviour
Description
--source include/have_innodb.inc
|
|
|
CREATE TABLE t (a INT PRIMARY KEY) ENGINE=InnoDB; |
INSERT INTO t VALUES (1),(2); |
|
|
SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE; |
SET innodb_snapshot_isolation = ON; |
CREATE TABLE t2 (b BLOB, UNIQUE(b)) ENGINE=InnoDB AS SELECT a AS b FROM t; |
|
|
DROP TABLE t, t2; |
|
10.6 8882f8fe6c5a87e2b367e260627af88ce9130d44 |
mysqltest: At line 8: query 'CREATE TABLE t2 (b BLOB, UNIQUE(b)) ENGINE=InnoDB AS SELECT a AS b FROM t' failed: HA_ERR_TABLE_DEF_CHANGED (159): InnoDB: insufficient history for index 0 |
2026-02-23 22:48:32 4 [ERROR] InnoDB: DROP TABLE `test`.`t2`: Record changed
|
The error started happening after this commit in 10.6.23:
commit 7fbbbc983f054a9c9c7f36ea8a9778ff3793a151
|
Author: Marko Mäkelä
|
Date: Fri Jul 11 16:07:08 2025 +0300
|
|
|
MDEV-36330: SERIALIZABLE read inconsistency
|
|
At TRANSACTION ISOLATION LEVEL SERIALIZABLE, InnoDB would fail to flag
|
Attachments
Issue Links
- is caused by
-
MDEV-36330 AUTO_INCREMENT leads to non-serializable on results
-
- Closed
-
- relates to
-
MDEV-371 Unique indexes for blobs
-
- Closed
-