Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
Because the InnoDB implementation in MariaDB has diverged from MySQL, it is not meaningful to report a MySQL version number for InnoDB any more. Some examples:
- MariaDB 10.1 (which is based on MySQL 5.6) included encryption and variable-size page compression before MySQL 5.7 introduced them
- MariaDB 10.2 (based on MySQL 5.7) introduced persistent AUTO_INCREMENT (
MDEV-6076) in a GA release before MySQL 8.0 - MariaDB 10.3 (based on MySQL 5.7) introduced instant ADD COLUMN (
MDEV-11369) before MySQL
All of these features use a different implementation and file format. Also, some features were never merged from MySQL 5.7, and thus MariaDB is not affected by related bugs. Examples include CREATE TABLESPACE and the reimplementation of the partitioning engine.
Attachments
Issue Links
- blocks
-
MDEV-28554 Remove innodb_version
-
- Closed
-
- causes
-
MDEV-23141 PHP mysqli reports 'READ WRITE' and 'READ ONLY' in transaction is not supported.
-
- Closed
-
For some reason, the tests rpl.rpl_parallel2 and rpl.rpl_semi_sync_after_sync intermittently fail after the InnoDB version number was changed.
10.3 442a6e6b257e335f70730b0e18394c2f638f2962
CURRENT_TEST: rpl.rpl_parallel2
mysqltest: In included file "./include/rpl_init.inc":
included from /mariadb/10.3/mysql-test/suite/rpl/t/rpl_parallel2.test at line 6:
At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first
I have disabled these tests for now.