Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5
-
None
Description
The test case mainly represents upgrade through replication (old master => new slave), where the old master had a table with binary(16) for IPv6 values, while the new slave has inet6.
--source include/have_binlog_format_row.inc
|
--source include/master-slave.inc
|
|
create table t1 (a binary(16)); |
|
--sync_slave_with_master
|
alter table t1 modify a inet6; |
|
--connection master
|
insert into t1 values (inet6_aton('::')); |
|
--sync_slave_with_master
|
|
# Cleanup
|
--connection master
|
drop table t1; |
--source include/rpl_end.inc |
10.5 22b645ef |
Last_Errno 1030
|
Last_Error Could not execute Write_rows_v1 event on table test.t1; Got error 171 "The event was corrupt, leading to illegal data being read" from storage engine MyISAM, Error_code: 1030; handler error HA_ERR_CORRUPT_EVENT; the event's master log master-bin.000001, end_log_pos 655
|
Attachments
Issue Links
- relates to
-
MDEV-274 The data type for IPv6/IPv4 addresses in MariaDB
- Closed
-
MDEV-20784 Testing for MDEV-274 (INET6, data type for IPv6/IPv4 addresses)
- Closed