Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.2(EOL)
-
None
Description
|
Test case |
--source include/have_innodb.inc
|
|
|
--disable_warnings
|
DROP TABLE IF EXISTS t1; |
--enable_warnings
|
|
|
CREATE TABLE t1 (a INT, b CHAR(8)) ENGINE=InnoDB; |
INSERT INTO t1 (a,b) VALUES (1,'f'),(2,'b'); |
|
|
LOCK TABLE t1 READ; |
|
|
--connect (con0,localhost,root,,)
|
SET lock_wait_timeout = 1; |
--error ER_DELAYED_NOT_SUPPORTED
|
INSERT DELAYED INTO t1 (a,b) VALUES (3,'c'); |
|
|
# Cleanup
|
--disconnect con0
|
--connection default
|
UNLOCK TABLES;
|
DROP TABLE t1; |
In previous versions this test case would pass. Now instead of ER_DELAYED_NOT_SUPPORTED the INSERT DELAYED fails with ER_LOCK_WAIT_TIMEOUT.
Same happens with MERGE engine.
The change in behavior was introduced by this commit:
commit 8774a02364600279908bd9fb8b92d61dc4fcf60e
|
Author: Sergey Vojtovich <svoj@mariadb.org>
|
Date: Thu Dec 8 14:20:46 2016 +0400
|
|
|
MDEV-11227 - mysqlimport -l doesn't issue UNLOCK TABLES
|
It's not critical, but I want to make sure it was intentional, or at least expected side-effect.