Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.12, 10.3(EOL), 10.4(EOL), 10.5
-
Debian 9
Description
Hello,
I have this setup:
- master
- slave with system versioning activated
When I add a new column on master for a table, this is also propagated to slave , but when an update is running on master on that table and is replicated to slave, it fails, with error that it cannot change column type from my define type to timestamp(6). I have row based replication with GTID.
I have both secure timestamp=YES and system_versioning_alter_history=KEEP on the slave.
I have the same setup with mariadb 10.3.14 but replication is not going down.
What can be the cause ?
Attachments
Issue Links
- duplicates
-
MDEV-30430 Enabling system versioning on tables without primary key breaks replication
- Closed
- relates to
-
MDEV-12483 Add foreign keys support for partitioned tables
- Stalled
-
MDEV-14767 system_versioning_alter_history breaks ALTER replication
- Closed
-
MDEV-30430 Enabling system versioning on tables without primary key breaks replication
- Closed