| Server IP : 172.67.216.182 / Your IP : 162.158.162.44 Web Server : Apache System : Linux krdc-ubuntu-s-2vcpu-4gb-amd-blr1-01.localdomain 5.15.0-142-generic #152-Ubuntu SMP Mon May 19 10:54:31 UTC 2025 x86_64 User : www ( 1000) PHP Version : 7.4.33 Disable Function : passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /www/server/mysql/mysql-test/suite/group_replication/t/ |
Upload File : |
################################################################################ # 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 ../inc/have_group_replication_plugin.inc --source ../inc/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 ../inc/group_replication_end.inc