mirror of
https://github.com/MariaDB/server.git
synced 2025-01-21 06:22:28 +01:00
2b2ae926f4
if binlog_format=mixed
Addition to fix for BUG#34768: fixed test case failures discovered
by pushbuild.
mysql-test/suite/binlog/r/binlog_stm_ps.result:
Fixed binlog_stm_ps failure when binlog format is statement:
- this test case makes sence only if binlog format is statement,
thus execute it only in this mode;
- added a warning that insert ... select ... limit is not safe
to execute in statement mode.
mysql-test/suite/binlog/t/binlog_stm_ps.test:
Fixed binlog_stm_ps failure when binlog format is statement:
- this test case makes sence only if binlog format is statement,
thus execute it only in this mode;
- added a warning that insert ... select ... limit is not safe
to execute in statement mode.
mysql-test/suite/rpl/t/rpl_optimize.test:
rpl_optimize test may be executed in various binlog format modes.
In statement mode delete ... limit issues a warning, in mixed and
row modes it does not.
Fixed a test case so it is still possible to execute it in all binlog
format modes by ignoring delete ... limit warnings.
mysql-test/suite/rpl/t/rpl_user_variables.test:
rpl_user_variables test may be executed in various binlog format modes.
In statement mode insert ... select ... limit issues a warning,
in mixed and row modes it does not.
Fixed a test case so it is still possible to execute it in all binlog
format modes by ignoring insert ... select ... limit warnings.
56 lines
1.8 KiB
Text
56 lines
1.8 KiB
Text
# Test for BUG#1858 "OPTIMIZE TABLE done by a client
|
|
# thread stops the slave SQL thread".
|
|
# You can replace OPTIMIZE by REPAIR.
|
|
#####################################
|
|
# Change Author: JBM
|
|
# Change Date: 2006-02-09
|
|
# Change: NDB does not and will not support
|
|
# OPTIMIZE for memory tables. If and when
|
|
# it does support for Disk Data, a new
|
|
# version of this test will be need.
|
|
# Skipping this test if default engine = ndb
|
|
#####################################
|
|
-- source include/not_ndb_default.inc
|
|
-- source include/master-slave.inc
|
|
|
|
create table t1 (a int not null auto_increment primary key, b int, key(b));
|
|
INSERT INTO t1 (a) VALUES (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
INSERT INTO t1 (a) SELECT null FROM t1;
|
|
save_master_pos;
|
|
# a few updates to force OPTIMIZE to do something
|
|
update t1 set b=(a/2*rand());
|
|
--disable_warnings
|
|
delete from t1 order by b limit 10000;
|
|
--enable_warnings
|
|
|
|
connection slave;
|
|
sync_with_master;
|
|
optimize table t1;
|
|
connection master;
|
|
save_master_pos;
|
|
connection slave;
|
|
# Bug was that when the INSERT terminated on slave,
|
|
# the slave SQL thread got killed by OPTIMIZE.
|
|
sync_with_master; # won't work if slave SQL thread stopped
|
|
|
|
connection master; # cleanup
|
|
drop table t1;
|
|
connection slave;
|
|
sync_with_master;
|
|
|
|
# If the machine is so fast that slave syncs before OPTIMIZE
|
|
# starts, this test wil demonstrate nothing but will pass.
|
|
|
|
# End of 4.1 tests
|