Server IP : 104.21.38.3 / Your IP : 172.70.143.4 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/binlog/t/ |
Upload File : |
# # Tests of innodb/binlog with the row binlog format # source include/have_innodb.inc; source include/have_myisam.inc; source include/have_log_bin.inc; source include/have_binlog_format_row.inc; # # Bug #40221 Replication failure on RBR + UPDATE the primary key # CREATE TABLE t1 (i int unique) ENGINE=innodb; reset master; # part 1: update can cause the dup key begin; insert into t1 values (1),(2); --echo *** the following UPDATE query wont generate any updates for the binlog *** --error ER_DUP_ENTRY update t1 set i = 3 where i < 3; commit; --echo *** Results of the test: the binlog must have only Write_rows events not any Update_rows *** source include/show_binlog_events.inc; # part 2: insert can cause the dup key delete from t1; reset master; begin; insert into t1 values (1),(2); --echo *** the following UPDATE query wont generate any updates for the binlog *** --error ER_DUP_ENTRY insert into t1 values (3),(4),(1),(2); commit; --echo *** Results of the test: the binlog must have only one Write_rows event not two *** source include/show_binlog_events.inc; drop table t1; # # BUG#51251 # # The test case checks if truncating a temporary table created with # engine InnoDB will not cause the truncate statement to be binlogged. # Before patch for BUG#51251, the TRUNCATE statements below would be # binlogged, which would cause the slave to fail with "table does not # exist". RESET MASTER; CREATE TABLE t1 ( c1 int , primary key (c1)) ENGINE=InnoDB; INSERT INTO t1 VALUES (1), (2), (3); CREATE TEMPORARY TABLE IF NOT EXISTS t2 LIKE t1; TRUNCATE TABLE t2; DROP TABLE t1; -- echo ############################################### -- echo ### assertion: No event for 'TRUNCATE TABLE t2' -- echo ############################################### -- source include/show_binlog_events.inc -- echo ############################################### RESET MASTER; CREATE TEMPORARY TABLE t1 (c1 int) Engine=InnoDB; INSERT INTO t1 VALUES (1), (2), (3); TRUNCATE t1; DROP TEMPORARY TABLE t1; -- echo ############################################### -- echo ### assertion: No event for 'TRUNCATE TABLE t1' -- echo ############################################### -- source include/show_binlog_events.inc -- echo ############################################### --echo # --echo # Bug#12346411 SQL/LOG.CC:6509: ASSERTION `PREPARED_XIDS > 0' FAILED --echo # --disable_warnings DROP TABLE IF EXISTS t1, t2; --enable_warnings CREATE TABLE t1(a INT PRIMARY KEY) engine=innodb; CREATE TABLE t2(a INT) engine=myisam; INSERT INTO t1 VALUES (1); START TRANSACTION; INSERT INTO t2 VALUES (1); INSERT IGNORE INTO t1 VALUES (1); COMMIT; INSERT INTO t1 VALUES (2); START TRANSACTION; INSERT INTO t2 VALUES (2); UPDATE IGNORE t1 SET a=1 WHERE a=2; COMMIT; DROP TABLE t1, t2;