mirror of
https://github.com/MariaDB/server.git
synced 2025-01-18 13:02:28 +01:00
539e2130b0
The idea of the fix is that the administrative statements OPTIMIZE TABLE, REPAIR TABLE and ANALYZE TABLE should not generate binlog errors if there is no errors on the master. sql/sql_parse.cc: No binlog error generated sql/sql_table.cc: Documentation BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
15 lines
441 B
Text
15 lines
441 B
Text
stop slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
start slave;
|
|
CREATE TABLE t1 ( a int ) ENGINE=InnoDB;
|
|
BEGIN;
|
|
INSERT INTO t1 VALUES (1);
|
|
OPTIMIZE TABLE t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 optimize status Operation failed
|
|
OPTIMIZE TABLE non_existing;
|
|
Table Op Msg_type Msg_text
|
|
test.non_existing optimize error Table 'test.non_existing' doesn't exist
|