diff options
| author | Rinat Ibragimov <ri@tempesta-tech.com> | 2020-10-21 23:34:36 +0300 |
|---|---|---|
| committer | Monty <monty@mariadb.org> | 2020-10-22 00:18:33 +0300 |
| commit | 709ba7dcae871e365697f67677c908b55ad4a964 (patch) | |
| tree | dde2860dddbc468d6f1a4484b8e109baff7226a5 /sql/sql_class.cc | |
| parent | ac8d20579512e05001f9bf8193187e47c870d35a (diff) | |
| download | mariadb-git-709ba7dcae871e365697f67677c908b55ad4a964.tar.gz | |
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
Diffstat (limited to 'sql/sql_class.cc')
| -rw-r--r-- | sql/sql_class.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/sql_class.cc b/sql/sql_class.cc index e57196ee056..ab9a0118bde 100644 --- a/sql/sql_class.cc +++ b/sql/sql_class.cc @@ -2569,7 +2569,7 @@ void THD::give_protection_error() my_error(ER_BACKUP_LOCK_IS_ACTIVE, MYF(0)); else { - DBUG_ASSERT(global_read_lock.is_acquired()); + DBUG_ASSERT(global_read_lock.is_acquired() || mdl_backup_lock); my_error(ER_CANT_UPDATE_WITH_READLOCK, MYF(0)); } } |