[MDEV-28554] Remove innodb_version Created: 2022-05-13  Updated: 2023-08-04  Resolved: 2022-06-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.10.0

Type: Task Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-16172 Remove InnoDB 5.7 version number from... Closed
Problem/Incident
causes MDEV-31847 Global variable innodb_version missing Closed

 Description   

Until MDEV-16172 was implemented in MariaDB Server 10.3.7, InnoDB used to report a MySQL based version number at startup. Since then, the startup message reported a MariaDB version number, like this:

mariadb-10.6.7

 
2022-05-13  8:41:09 0 [Note] InnoDB: 10.6.7 started; log sequence number 0; transaction id 3

That version number was already reported by an earlier message:

mariadb-10.6.7

 
2022-05-13  8:41:09 0 [Note] /dev/shm/10.6/sql/mariadbd (server 10.6.7-MariaDB-debug) starting as process 23497 ...

Let us remove the redundant version number from InnoDB startup messages.

Note: At the start of the InnoDB redo log file ib_logfile0 there will continue to be a string that reports the program version with which the log file was created or rebuilt.

 Comments   
Comment by Marko Mäkelä [ 2022-05-13 ]

The start-up message was cleaned up already in MDEV-14425, so that it will indicate whether the redo log interface uses mmap(2):

mariadb-10.8.1

 
2022-05-13 15:35:21 0 [Note] InnoDB: log sequence number 0 (memory-mapped); transaction id 3

But, there is a global variable innodb_version that was always identical with the server version number. That one will be removed as part of this task.

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