Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.6, 10.11, 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4, 11.5(EOL)
Description
# Reproduces fine with MBR and SBR, but not RBR. Requires standard m/s setup. |
CREATE TEMPORARY TABLE t1 (c INT) ENGINE=InnoDB; |
CREATE TABLE t2 (c DATE) ENGINE=MyISAM PARTITION BY LIST (YEARWEEK(c)) (PARTITION p VALUES IN (1,2)); |
CREATE TABLE t3 (c INT); |
CREATE TRIGGER tr1 AFTER INSERT ON t3 FOR EACH ROW INSERT INTO t2 VALUES (1); |
XA START 'a'; |
INSERT INTO t3 VALUES(); |
DELETE FROM mysql.proc LIMIT 1; # Likely other queries can be used; it is just a state trigger it seems |
Leads to:
11.5.0 3f9182126c64bcec359bebe9ebad2a0e559b13e2 (Debug) |
2024-04-27 15:08:46 5 [Note] Slave I/O thread: connected to master 'repl_user@127.0.0.1:11313',replication starts at GTID position ''
|
2024-04-27 15:08:48 6 [ERROR] Slave SQL: Error executing row event: 'You can't combine write-locking of system tables with other tables or lock types', Gtid 0-1-8, Internal MariaDB error code: 1428
|
2024-04-27 15:08:48 6 [Warning] Slave: You can't combine write-locking of system tables with other tables or lock types Error_code: 1428
|
2024-04-27 15:08:48 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.000001' position 1633; GTID position '0-1-7'
|
Tested present in 10.5 (opt+dbg), 11.3 (opt), 11.4 (opt+dbg) and 11.5 (dbg); assumed to be in other versions also, though issue may be lightly sporadic.