[MDEV-15403] Slave stops with ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE upon UPDATE on versioned table Created: 2018-02-24  Updated: 2018-02-24  Resolved: 2018-02-24

Status: Closed
Project: MariaDB Server
Component/s: Replication, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.3.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None


 Description   

--source include/have_binlog_format_mixed.inc
--source include/master-slave.inc
 
CREATE TABLE t1 (a INT) WITH SYSTEM VERSIONING;
INSERT INTO t1 VALUES (1);
 
CREATE TEMPORARY TABLE tmp (b INT);
SET SESSION optimizer_switch= REPLACE( @@optimizer_switch, '=on', '=off' );
UPDATE t1 SET a = 2;
 
--sync_slave_with_master

10.3 8f9c64000eef2

2018-02-24  4:21:47 12 [ERROR] Slave SQL: Error executing row event: 'Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging', Gtid 0-1-4, Internal MariaDB error code: 1664
2018-02-24  4:21:47 12 [Warning] Slave: Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging Error_code: 1664
2018-02-24  4:21:47 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000001' position 834


Generated at Thu Feb 08 08:21:02 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.