| Server IP : 104.21.38.3 / Your IP : 172.69.166.54 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/src/mysql-test/suite/engines/funcs/t/ |
Upload File : |
################################ # Change Author: JBM # Change Date: 2006-01-12 # Change: Added back have stm binlog # and added requirments comments ################################ # test case to make slave thread get ahead by 22 bytes ################################ #REQUIREMENT: If there is a faked slave duplicate key insert #error and the slave is restarted, the replication should #proceed in a correct way. ################################ #REQUIREMENT: If there is a faked slave non-existing record #delete error and the slave is restarted, then the replication #should proceed in a correct way. ################################# -- source include/have_binlog_format_mixed_or_statement.inc -- source include/master-slave.inc # first, cause a duplicate key problem on the slave create table t1(n int auto_increment primary key, s char(10)); sync_slave_with_master; insert into t1 values (2,'old'); connection master; insert into t1 values(NULL,'new'); insert into t1 values(NULL,'new'); save_master_pos; connection slave; # wait until the slave tries to run the query, fails and aborts slave thread wait_for_slave_to_stop; select * from t1 order by n; delete from t1 where n = 2; --disable_warnings start slave; --enable_warnings sync_with_master; #now the buggy slave would be confused on the offset but it can replicate #in order to make it break, we need to stop/start the slave one more time stop slave; connection master; # to be able to really confuse the slave, we need some non-auto-increment # events in the log create table t2(n int); drop table t2; insert into t1 values(NULL,'new'); # what happens when we delete a row which does not exist on slave? set sql_log_bin=0; insert into t1 values(NULL,'new'); set sql_log_bin=1; delete from t1 where n=4; save_master_pos; connection slave; --disable_warnings start slave; --enable_warnings #now the truth comes out - if the slave is buggy, it will never sync because #the slave thread is not able to read events sync_with_master; select * from t1 order by n; #clean up connection master; drop table t1; sync_slave_with_master; # End of 4.1 tests