Details
-
Bug
-
Status: In Progress (View Workflow)
-
Critical
-
Resolution: Unresolved
-
10.0.8, 10.4(EOL), 10.5, 10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4
Description
In the provided test case, before I run INSERT, I execute a seemingly harmless, albeit useless, ALTER on a non-existent table, which expectedly fails with ER_NO_SUCH_TABLE.
But after that, the next INSERT on the existing table fails with ER_WRONG_PARTITION_NAME. It is expected to fail, but without the previous unrelated ALTER it fails with ER_NO_PARTITION_FOR_GIVEN_VALUE.
It wouldn't be so bad, but the whole sequence is executed on a master, the failed ALTER isn't written to the binary log, but INSERT might be, for example if it's run on a non-transactional table. In this case INSERT is written with ER_WRONG_PARTITION_NAME, but on a slave it causes ER_NO_PARTITION_FOR_GIVEN_VALUE, and this discrepancy causes replication failure.
--source include/have_partition.inc
|
--source include/master-slave.inc
|
--source include/have_binlog_format_statement.inc
|
|
|
CREATE TABLE IF NOT EXISTS t1 (a INT) |
ENGINE=MyISAM
|
PARTITION BY LIST(a) ( |
PARTITION p0 VALUES IN (9, NULL), |
PARTITION p1 VALUES IN (8, 2, 7), |
PARTITION p2 VALUES IN (6, 4, 5), |
PARTITION p3 VALUES IN (3, 1, 0) |
);
|
ALTER TABLE t1 DROP PARTITION p0; |
|
|
####### Game changer
|
--error ER_NO_SUCH_TABLE
|
ALTER TABLE non_existent TRUNCATE PARTITION p1,p2; |
#######
|
|
|
--error ER_NO_PARTITION_FOR_GIVEN_VALUE,ER_WRONG_PARTITION_NAME
|
INSERT INTO t1 PARTITION (p1,p2,p3) VALUES (0),(9); |
SHOW WARNINGS;
|
|
|
--sync_slave_with_master
|
140305 23:11:27 [ERROR] Slave SQL: Query caused different errors on master and slave. Error on master: message (format)='Incorrect partition name' error code=1567 ; Error on slave: actual message='Table has no partition for value 9', error code=1526. Default database: 'test'. Query: 'INSERT INTO t1 PARTITION (p1,p2,p3) VALUES (0),(9)', Internal MariaDB error code: 0
|
140305 23:11:27 [ERROR] Slave SQL: Table has no partition for value 9, Internal MariaDB error code: 1526
|