File: gr_skip_performance_schema_dml.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (23 lines) | stat: -rw-r--r-- 1,076 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 
################################################################################
# This test verifies the behavior of the dml opertions in group_replication.
# Since performance schema tables are not logged in the binary log, they
# should not be used during the compatibility check for the Group replication.
# Therefore it should not cause any error during DML operations to tables in
# the performance schema database.
#
# Test:
# 0. The test requires one server.
# 1. With a member ONLINE, try executing UPDATE on a P_S table. It should not
#    error out.
################################################################################

--source include/have_group_replication_plugin.inc
--source include/group_replication.inc

--let $rpl_connection_name= server1
--source include/rpl_connection.inc

--echo # This should not error out as performance schema tables are not used in the before dml hook process.
UPDATE performance_schema.setup_instruments SET ENABLED='YES', TIMED='YES' WHERE name='wait/lock/metadata/sql/mdl';

--source include/group_replication_end.inc