Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.4, 11.6(EOL), 11.7
Description
SET GLOBAL innodb_buffer_pool_size=12*1024*1024; |
CREATE TABLE t1 (d DOUBLE); |
INSERT INTO t1 VALUES (0x0061),(0x0041),(0x00E0),(0x00C0),(0x1EA3),(0x1EA2),(0x00E3),(0x00C3),(0x00E1),(0x00C1),(0x1EA1),(0x1EA0); |
INSERT INTO t1 SELECT t1.* FROM t1,t1 t2,t1 t3,t1 t4,t1 t5,t1 t6; |
Will lead to:
10.10.0 081a284712bb661349e2e3802077b12211cede3e (Optimized) |
10.10.0-opt>INSERT INTO t1 SELECT t1.* FROM t1,t1 t2,t1 t3,t1 t4,t1 t5,t1 t6;
|
ERROR 1206 (HY000): The total number of locks exceeds the lock table size
|
In 10.6 to 10.10 only.
Note that in this ticket, unlike MDEV-28800, no initial innodb-buffer-pool-size is set, though the buffer pool is resized in the same was as MDEV-28800.
Attachments
Issue Links
- relates to
-
MDEV-24813 Locking full table scan fails to use table-level locking
- In Review
-
MDEV-25342 autosize innodb_buffer_pool_chunk_size
- Closed
-
MDEV-28805 SET GLOBAL innodb_buffer_pool_size=12*1024*1024 has different outcomes depending on version
- Closed
-
MDEV-28800 SIGABRT due to running out of memory for InnoDB locks
- Closed
-
MDEV-28804 Increased lock objects in 10.6+ leading to significant slowdown when using a limited InnoDB buffer pool, including in release builds
- Stalled
-
MDEV-33324 insert ... select from joins hangs or result in 1206: The total number of locks exceeds the lock table size
- Open