Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
None
-
None
-
Can result in hang or crash
Description
Essentially, the following test:
1. sets slave_run_triggers_for_rbr=LOGGING
2. Creates a AFTER UPDATE trigger on slave
3. Replicates the update event
In the event of absence of triggers on master, assertion fails.
--source include/have_binlog_format_row.inc
|
--source include/have_innodb.inc
|
--source include/master-slave.inc
|
SET default_storage_engine=InnoDB; |
--connection slave
|
STOP SLAVE;
|
SET GLOBAL slave_run_triggers_for_rbr=LOGGING; |
--source include/start_slave.inc
|
--connection master
|
CREATE TABLE t1 (a TEXT); |
CREATE TABLE t3 (a TEXT); |
|
|
create table t2 (c int primary key, a text ) engine=innodb; |
|
|
insert t2(c) values(1), (0); |
insert t3 values(NULL); |
--connection slave
|
CREATE TRIGGER tr AFTER UPDATE ON t3 FOR EACH ROW INSERT INTO t1 SELECT a from t2; |
--connection master
|
UPDATE t3 set a = 'updated'; |
select * from t1; |
--sync_slave_with_master
|
connection slave; |
select * from t1; |
DROP TABLE t1,t2; # Cleanup |
--source include/rpl_end.inc |
Attachments
Issue Links
- relates to
-
MDEV-38937 GTT: 1944 Error executing row event: 'Failed to open t2.test' on INSERT
-
- In Review
-