MySQL Bugs: #68177: innodb_log_file_size with wrong default value

Bug #68177	innodb_log_file_size with wrong default value
Submitted:	25 Jan 2013 4:44	Modified:	11 Mar 2013 16:41
Reporter:	lou shuai (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.6.*	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
When downgrade to 5.5 from 5.6, the 5.5 server can not startup with the same data ,the reason is that the innodb log file size mismatched.
But the configuration file did not config the innodb_log_file_size option, so both 5.5 and 5.6 use the default value which is the same value 5242880 described in manuals.

Actually the default value changed in mysql 5.6, so the document should change too.

How to repeat:
mysql> select version(); show variables like 'innodb_log_file_size';
+--------------------+
| version()          |
+--------------------+
| 5.6.9-rc-debug-log |
+--------------------+
1 row in set (0.04 sec)

+----------------------+----------+
| Variable_name        | Value    |
+----------------------+----------+
| innodb_log_file_size | 50331648 |
+----------------------+----------+
1 row in set (0.00 sec)

As seen above, the default value is not the same as 5.5.

Suggested fix:
Just fix the document.

Indeed, i expected to see this documented in at least two places:

http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_log_file_size

http://dev.mysql.com/doc/refman/5.6/en/innodb-parameter-changes.html#innodb-parameters-new...

@Shane Bester

Yes, both the two places should document this change.

Checking the source, this value changes from 5MB to 48MB (50331648) in 5.6.8.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Updating both placed to reflect new default as of 5.6.8.