File: rpl_sv_relay_space.test

package info (click to toggle)
mysql-5.5 5.5.42-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 201,212 kB
  • sloc: cpp: 646,036; ansic: 551,342; perl: 53,243; pascal: 25,099; yacc: 13,059; sh: 10,248; cs: 4,647; xml: 4,178; sql: 3,193; makefile: 1,368; lex: 639; awk: 54
file content (25 lines) | stat: -rw-r--r-- 881 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
source include/master-slave.inc;

#
# Bug#7100 relay_log_space_max missing from SHOW VARIABLES
#
SHOW VARIABLES LIKE 'relay_log_space_limit';

# Matz says: I have no idea what this is supposed to test, but it has
# potential for generating different results with some storage engines
# that process rows in an order not dependent on the insertion order.
# For instance, I would assume that distributed storage engines (like
# NDB) could process rows based on locality.

eval CREATE TABLE t1 (name varchar(64), age smallint(3))ENGINE=$engine_type;
INSERT INTO t1 SET name='Andy', age=31;
INSERT INTO t1 SET name='Jacob', age=2;
INSERT INTO t1 SET name='Caleb', age=1;
ALTER TABLE t1 ADD id int(8) ZEROFILL AUTO_INCREMENT PRIMARY KEY;
SELECT * FROM t1 ORDER BY id;
sync_slave_with_master;
SELECT * FROM t1 ORDER BY id;
connection master;
DROP TABLE t1;

--source include/rpl_end.inc