| Server IP : 172.67.216.182 / Your IP : 162.158.106.252 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/extra/rpl_tests/ |
Upload File : |
# Both of the following tests check that comparison of binlog BI # against SE record will not fail due to remains from previous values # in the SE record (before a given field was set to null). # # In MIXED mode: # - Insert and update are executed as statements # - Delete is executed as a row event # - Assertion: checks that comparison will not fail because the update # statement will clear the record contents for the nulled # field. If data was not cleared, some engines may keep # the value and return it later as garbage - despite the # fact that field is null. This may cause slave to # falsely fail in the comparison (memcmp would fail # because of "garbage" in record data). # # In ROW mode: # - Insert, update and delete are executed as row events. # - Assertion: checks that comparison will not fail because the update # rows event will clear the record contents before # feeding the new value to the SE. This protects against # SEs that do not clear record contents when storing # nulled fields. If the engine did not clear the data it # would cause slave to falsely fail in the comparison # (memcmp would fail because of "garbage" in record # data). This scenario is pretty much the same described # above in MIXED mode, but checks different execution # path in the slave. # BUG#49481: RBR: MyISAM and bit fields may cause slave to stop on # delete cant find record -- source include/rpl_reset.inc -- connection master -- eval CREATE TABLE t1 (c1 BIT, c2 INT) Engine=$engine INSERT INTO `t1` VALUES ( 1, 1 ); UPDATE t1 SET c1=NULL where c2=1; -- source include/sync_slave_sql_with_master.inc -- let $diff_tables= master:t1, slave:t1 -- source include/diff_tables.inc -- connection master # triggers switch to row mode when on mixed DELETE FROM t1 WHERE c2=1 LIMIT 1; -- source include/sync_slave_sql_with_master.inc -- let $diff_tables= master:t1, slave:t1 -- source include/diff_tables.inc -- connection master DROP TABLE t1; -- source include/sync_slave_sql_with_master.inc -- source include/rpl_reset.inc -- connection master # BUG#49482: RBR: Replication may break on deletes when MyISAM tables # + char field are used -- eval CREATE TABLE t1 (c1 CHAR) Engine=$engine INSERT INTO t1 ( c1 ) VALUES ( 'w' ) ; SELECT * FROM t1; UPDATE t1 SET c1=NULL WHERE c1='w'; -- source include/sync_slave_sql_with_master.inc -- let $diff_tables= master:t1, slave:t1 -- source include/diff_tables.inc -- connection master # triggers switch to row mode when on mixed DELETE FROM t1 LIMIT 2; -- source include/sync_slave_sql_with_master.inc -- let $diff_tables= master:t1, slave:t1 -- source include/diff_tables.inc -- connection master DROP TABLE t1; -- source include/sync_slave_sql_with_master.inc