Skip to content

Commit 21d31b9

Browse files
committed
MDEV-26529: binlog.binlog_flush_binlogs_delete_domain fails on RISC-V
Per https://bugs.gentoo.org/807995 The test failed with: CURRENT_TEST: binlog.binlog_flush_binlogs_delete_domain — /tmp/mariadb-10.5.11/mysql-test/suite/binlog/r/binlog_flush_binlogs_delete_domain.result 2021-06-18 18:19:11.000000000 +0800 +++ /tmp/mariadb-10.5.11/mysql-test/suite/binlog/r/binlog_flush_binlogs_delete_domain.reject 2021-09-01 22:55:29.406655479 +0800 @@ -85,6 +85,6 @@ ERROR HY000: The value of gtid domain being deleted ('4294967296') exceeds its maximum size of 32 bit unsigned integer FLUSH BINARY LOGS DELETE_DOMAIN_ID = (4294967295); Warnings: -Warning 1076 The gtid domain being deleted ('4294967295') is not in the current binlog state +Warning 1076 The gtid domain being deleted ('18446744073709551615') is not in the current binlog state DROP TABLE t; RESET MASTER; mysqltest: Result length mismatch ptr_domain_id is a uint32* so explicitly cast this when printing it out. Thanks Marek Szuba for the bug report and testing the patch.
1 parent f554770 commit 21d31b9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

sql/rpl_gtid.cc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1859,7 +1859,7 @@ rpl_binlog_state::drop_domain(DYNAMIC_ARRAY *ids,
18591859
push_warning_printf(current_thd, Sql_condition::WARN_LEVEL_WARN,
18601860
ER_BINLOG_CANT_DELETE_GTID_DOMAIN,
18611861
"The gtid domain being deleted ('%lu') is not in "
1862-
"the current binlog state", *ptr_domain_id);
1862+
"the current binlog state", (unsigned long) *ptr_domain_id);
18631863
continue;
18641864
}
18651865

0 commit comments

Comments
 (0)