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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
# === Purpose ===
#
# This test verifies that ORDER BY on replication pfs tables returns
# the correct data set.
#
# === Implementation ===
#
# 1) Setup a multi-source replication topology.
# 2) With STS, execute DDLs on both the masters and use SQL ordering
# on PFS tables on slave.
# 3) Repeat step 2 with Multi-threaded Slave.
#
# === References ===
# Bug #22958077: ORDER BY LAST_SEEN_TRANSACTION RESULTS IN EMPTY SET (OR DEBUG
# ASSERTION)
# Test requires master-info-repository=TABLE, relay-log-info-repository=TABLE
--source include/have_slave_repository_type_table.inc
--let $rpl_topology= 3->2,1->2
--let $rpl_multi_source= 1
--let $rpl_skip_start_slave= 1
--source include/rpl_init.inc
--let $rpl_connection_name= server_2
--source include/rpl_connection.inc
SET @save.replica_parallel_workers= @@global.replica_parallel_workers;
--echo # Test for Single Threaded Slave
SET GLOBAL replica_parallel_workers= 0;
START SLAVE;
--source extra/rpl_tests/rpl_perfschema_order_by.test
--echo # Test for Multi Threaded Slave
STOP SLAVE;
SET GLOBAL replica_parallel_workers = 2;
START SLAVE;
--source extra/rpl_tests/rpl_perfschema_order_by.test
#Cleanup
STOP SLAVE;
--disable_warnings
SET @@global.replica_parallel_workers= @save.replica_parallel_workers;
--enable_warnings
START SLAVE;
--let $rpl_skip_sync= 1
--source include/rpl_end.inc
|
