mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
e9b8feef32
This assert could be triggered during two phase commit if binary log was used as transaction coordinator log. The triggered assert checks that the same number of transaction IDs are processed in the prepare and commit phases. The reason it was triggered, was that the transaction consisted of an INSERT/UPDATE IGNORE that had an ignorable error. Since it had an error, no row log events were made and therefore prepared_xids was 0. However, since it was an IGNORE statement, the statement started a read/write statement transaction, committed it and completed successfully. This patch fixes the problem by adjusting the assert to take this possibility into account. Test case added to binlog.binlog_innodb_row.test.
105 lines
2.7 KiB
Text
105 lines
2.7 KiB
Text
#
|
|
# Tests of innodb/binlog with the row binlog format
|
|
#
|
|
source include/have_innodb.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;
|