[MDEV-24273] System versioning replication fails when adding column on master - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.4.12, 10.3(EOL), 10.4(EOL), 10.5(EOL)
Fix Version/s: 10.3.35, 10.4.25, 10.5.16, 10.6.8
Component/s: Replication, Versioned Tables
Labels:
- ProductionIssue
- ProductionStory
Environment:
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 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

Activity

People

Assignee:: Aleksey Midenkov

Reporter:: Catalin Dumitriu

Votes:: 2 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2020-11-24 13:23

Updated:: 2023-08-22 13:10

Resolved:: 2023-08-21 00:34

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.