From 709ba7dcae871e365697f67677c908b55ad4a964 Mon Sep 17 00:00:00 2001 From: Rinat Ibragimov Date: Wed, 21 Oct 2020 23:34:36 +0300 Subject: MDEV-20945: BACKUP UNLOCK + FTWRL assertion failure MDEV-20945: BACKUP UNLOCK + FTWRL assertion failure | SIGSEGV in I_P_List from MDL_context::release_lock on INSERT w/ BACKUP LOCK (on optimized builds) | Assertion `ticket->m_duration == MDL_EXPLICIT' failed BACKUP LOCK behavior is modified so it won't be used wrong: - BACKUP LOCK should commit any active transactions. - BACKUP LOCK should not be allowed in stored procedures. - When BACKUP LOCK is active, don't allow any DDL's for that connection. - FTWRL is forbidden on the same connection while BACKUP LOCK is active. Reviewed-by: monty@mariadb.com --- mysql-test/main/implicit_commit.test | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'mysql-test/main/implicit_commit.test') diff --git a/mysql-test/main/implicit_commit.test b/mysql-test/main/implicit_commit.test index bcc43865395..09f2e2e921e 100644 --- a/mysql-test/main/implicit_commit.test +++ b/mysql-test/main/implicit_commit.test @@ -1114,6 +1114,16 @@ source include/implicit_commit_helper.inc; # backup database db1 to 'backup_db1.ba'; #source include/implicit_commit_helper.inc; +--echo # +--echo # SQLCOM_BACKUP_LOCK +--echo # + +INSERT INTO db1.trans VALUES (1); +BACKUP LOCK t1; +ROLLBACK; +BACKUP UNLOCK; +CALL db1.test_if_commit(); + --echo # --echo # SQLCOM_SHOW_ARCHIVE --echo # -- cgit v1.2.1