Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4, 10.5, 10.6, 10.9, 10.10, 10.11, 11.0, 11.1
Description
This issue is seen very often in the test runs. There are likely various other paths to reproduce the same issue. It seems to be a locking vs temporary tables oversight.
INSTALL PLUGIN Spider SONAME 'ha_spider.so'; |
CREATE SERVER srv FOREIGN DATA WRAPPER MYSQL OPTIONS (SOCKET '../socket.sock',DATABASE'',USER'',PASSWORD''); |
CREATE TABLE t (c INT) ENGINE=InnoDB; |
CREATE TABLE tm (c INT) ENGINE=InnoDB; |
CREATE TABLE t1 (c INT KEY) ENGINE=Spider COMMENT='WRAPPER "mysql",srv "srv",TABLE "t"'; |
CREATE TABLE t2 (c INT) ENGINE=Spider COMMENT='WRAPPER "mysql",srv "srv",TABLE "tm"'; |
LOCK TABLES t1 READ; # Not required, but proves incorrect outcome |
CREATE TEMPORARY TABLE t1 (c1 INT); |
LOCK TABLES t2 READ; |
DROP TABLE t1; |
LOCK TABLES non_existing WRITE;
|
SELECT 1 FROM t1; |
Leads to:
|
11.1.0 4e5b771e980edfdad5c5414aa62c81d409d585a4 (Debug) |
11.1.0-dbg>SELECT 1 FROM t1;
|
ERROR 1100 (HY000): Table 't' was not locked with LOCK TABLES
|
|
11.1.0 4e5b771e980edfdad5c5414aa62c81d409d585a4 (Debug) |
2023-06-06 14:26:13 4 [ERROR] Got error 1100 when reading table './test/t1'
|
Interestingly, when we remove only the KEY from col c in CREATE TABLE t1, the error shows at the command line,* but not in the error log*. This is an additional inconsistency (or bug).
Bug (or feature/syntax) confirmed present in:
MariaDB: 10.4.30 (dbg), 10.4.30 (opt), 10.5.21 (dbg), 10.5.21 (opt), 10.6.14 (dbg), 10.6.14 (opt), 10.9.7 (dbg), 10.9.7 (opt), 10.10.5 (dbg), 10.10.5 (opt), 10.11.4 (dbg), 10.11.4 (opt), 11.0.2 (dbg), 11.0.2 (opt), 11.1.0 (dbg), 11.1.0 (opt)