| Bug #63435 | InnoDB Plugin were changed, but still use the same version number 1.0.17 | ||
|---|---|---|---|
| Submitted: | 26 Nov 2011 9:04 | Modified: | 26 Dec 2012 20:12 |
| Reporter: | Meiji KIMURA | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S3 (Non-critical) |
| Version: | MySQL 5.1.58 or later | OS: | Any |
| Assigned to: | Vasil Dimov | CPU Architecture: | Any |
| Tags: | @@innodb_version, 1.0.17, InnoDB plugin | ||
[26 Nov 2011 12:12]
Valeriy Kravchuk
Indeed: macbook-pro:5.1 openxs$ bin/mysql -uroot testWelcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.1.60 Source distribution Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> select @@innodb_version; +------------------+ | @@innodb_version | +------------------+ | 1.0.17 | +------------------+ 1 row in set (0.00 sec)
[23 Apr 2012 12:26]
Meiji KIMURA
The situation is same In MySQL 5.1.61, 62. So I supposed that InnoDB Plugin's version '1.0.17' will be used forever.
[9 Dec 2012 15:43]
Meiji KIMURA
The situation is same In MySQL 5.1.66.
[26 Dec 2012 20:12]
John Russell
Added to changelog for 5.1.68, 5.5.30, 5.6.11: The value of the innodb_version variable was not updated consistently for all server releases for the InnoDB Plugin in MySQL 5.1, and the integrated InnoDB component in MySQL 5.5, 5.6, and higher. Since InnoDB and MySQL Server development cycles are fully integrated and synchronized, now the value returned by the innodb_version variable is the same as for the version variable.
Description: Recently, MySQL Document doesn't described about InnoDB Plugin version. I looked into this and the result is here. MySQL InnoDB Plugin 5.1.46 1.0.7(GA) 5.1.47 1.0.8(GA) 5.1.48 1.0.9(GA) 5.1.49 1.0.10(GA) 5.1.50 1.0.11(GA) 5.1.51 1.0.12(GA) 5.1.52 1.0.13(GA) 5.1.53 ↑ 5.1.54 1.0.14(GA) 5.1.55 1.0.15(GA) 5.1.56 ↑ 5.1.57 1.0.16(GA) 5.1.58 1.0.17(GA) 5.1.59 ↑ 5.1.60 ↑ After MySQL 5.1.58, InnoDB Plugin uses the same version (1.0.17). But many commits were done for InnoDB Plugin. Thus, the different source/binary returns the same version for this statement.(In MySQL 5.1.58, 5.1.59, 5.1.60) mysql [localhost] {msandbox} ((none)) > select @@innodb_version -> ; +------------------+ | @@innodb_version | +------------------+ | 1.0.17 | +------------------+ 1 row in set (0.00 sec) It should returns the unique version number if source code of InnoDB plugin changes. How to repeat: (1) Install MySQL (2) Add these line for InnoDB Plugin. ignore-builtin-innodb plugin-load=innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_plugin.so;innodb_locks=ha_innodb_plugin.so;innodb_lock_waits=ha_innodb_plugin.so;innodb_cmp=ha_innodb_plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;innodb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset=ha_innodb_plugin.so (3) select @@innodb_version Suggested fix: When changing codes for innodb_plugin, it should increment its version number.