Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.5, 10.6, 10.11, 11.2(EOL), 11.4, 11.6(EOL)
-
None
Description
Note: I'm filing it as "minor", mostly to have it in JIRA so that it could be found when someone encounters it; I'm not sure that anything can be actually done about it, BLOCK_COMMIT does affect writing temporary table actions into binlog "by design", so the choice here would be either to produce an error or not to block disconnect until the path for DROP is clear, and the latter sounds even worse.
--source include/have_binlog_format_mixed.inc
|
|
--connect (con1,localhost,root,,)
|
CREATE TEMPORARY TABLE tmp1 AS SELECT 1; |
--connection default
|
CREATE TEMPORARY TABLE tmp2 AS SELECT 2; |
BACKUP STAGE START;
|
BACKUP STAGE BLOCK_COMMIT;
|
--disconnect con1 |
10.5 855c21eb99a5c6a6f9eb52eea6ce7d3279a9f8c3 |
2024-10-22 18:36:04 6 [ERROR] Failed to write the DROP statement for temporary tables to binary log
|
^ Found warnings in /mnt8t/bld/10.5-asan/mysql-test/var/log/mysqld.1.err
|
The error is about tmp1 table.
If instead of triggering the table drop by the disconnect, an explicit DROP TABLE is performed, the problem becomes clearer:
--source include/have_binlog_format_mixed.inc
|
|
--connect (con1,localhost,root,,)
|
CREATE TEMPORARY TABLE tmp1 AS SELECT 1; |
--connection default
|
CREATE TEMPORARY TABLE tmp2 AS SELECT 2; |
BACKUP STAGE START;
|
BACKUP STAGE BLOCK_COMMIT;
|
--connection con1
|
SET lock_wait_timeout=1; |
DROP TEMPORARY TABLE tmp1; |
CURRENT_TEST: bug.w1
|
mysqltest: At line 11: query 'DROP TEMPORARY TABLE tmp1' failed: 1205: Lock wait timeout exceeded; try restarting transaction |