database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-29 05:21:33 +03:00
Code Activity

Fix for MDEV-15812 Assert in SEQUENCE when forcing STATEMEMT format

Browse Source 
The bug was the we copied the lock type to the underlying engine even when
external_lock failed.
This commit is contained in:
Monty
2018-05-06 19:39:48 +03:00
parent 529c1a3b6c
commit 0bfd45f634
3 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
mysql-test/suite/sql_sequence/replication_drop.result Normal file
View File

@ -0,0 +1,5 @@
CREATE SEQUENCE seq ENGINE=InnoDB;
SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
INSERT INTO seq VALUES (1,1,100,1,1,1,1,1);
ERROR HY000: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
DROP SEQUENCE seq;

17
mysql-test/suite/sql_sequence/replication_drop.test Normal file
View File

@ -0,0 +1,17 @@
#
# Test for MDEV-15812
# Assertion `m_lock_type == 2' failed in
# handler::~handler on dropping a sequence after
# ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
#
--source include/have_innodb.inc
--source include/have_binlog_format_statement.inc
CREATE SEQUENCE seq ENGINE=InnoDB;
SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
--error ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
INSERT INTO seq VALUES (1,1,100,1,1,1,1,1);
# Cleanup
DROP SEQUENCE seq;