[MDEV-32059] mariadb-binlog should work between (almost) any release Created: 2023-08-31  Updated: 2023-11-30

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Michael Widenius Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-32053 New features requested by customer on... Open
relates to MDEV-32058 MariaDB server crashes when replicati... Open

 Description   

We should ensure that one can use the MariaDB binlogs as a form of 'incremental backup' between 'any' release that support the same MariaDB SQL syntax.

Providing support for earlier releases is important if upgrading to a new major release fails and the customer has to go back to an earlier release. In this case the binary logs may be the only way to recover all data!

If binary format for row events is changed in a incompatible way, we should to enhance MariaDB to write the row events as normal SQL events or alternatively consider adding an option like '--remote-server=10.6' that would change the output from mariadb-binlog to match data expected by the given server version.

In buildbot we should add test to test for mariadb-binlog to send data from the current version to next and previous major versions.



 Comments   
Comment by Kristian Nielsen [ 2023-08-31 ]

Note the MARIADB_SLAVE_CAPABILITY_* constants that are used to provide similar functionality to connecting slaves, and could probably be used for this also.

Generated at Thu Feb 08 10:28:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.