Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.5, 10.6, 10.11, 11.2, 11.4, 11.0(EOL), 11.5(EOL)
-
None
Description
both master and slave have the same configuration - with enforce_storage_engine=Aria , but they end up with tables that use different storage engine:
--source include/have_innodb.inc
|
--source include/master-slave.inc
|
|
--connection slave
|
SET sql_mode='',enforce_storage_engine=Aria; |
|
--connection master
|
SET sql_mode='',enforce_storage_engine=Aria; |
CREATE TABLE t1(i INT) ENGINE=INNODB; |
CREATE TABLE t2(i INT) ENGINE=MYISAM; |
|
--sync_slave_with_master
|
SHOW CREATE TABLE t1; |
SHOW CREATE TABLE t2; |
|
# Cleanup
|
--connection master
|
DROP TABLE t1, t2; |
--sync_slave_with_master
|
|
--source include/rpl_end.inc |
connection slave;
|
SHOW CREATE TABLE t1;
|
Table Create Table
|
t1 CREATE TABLE `t1` (
|
`i` int(11) DEFAULT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci
|
SHOW CREATE TABLE t2;
|
Table Create Table
|
t2 CREATE TABLE `t2` (
|
`i` int(11) DEFAULT NULL
|
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci
|
Attachments
Issue Links
- relates to
-
MDEV-9312 storage engine not enforced during galera cluster replication
- Closed