Bug #51901 | error message references internal variable name innobase_buffer_pool_size | ||
---|---|---|---|
Submitted: | 10 Mar 2010 6:47 | Modified: | 2 Jul 2013 14:42 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
Version: | 5.1.43, 5.1.44 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[10 Mar 2010 6:47]
Shane Bester
[10 Mar 2010 6:48]
MySQL Verification Team
same with this. "innobase_log_file_size can't be over 4GB"
[10 Mar 2010 7:01]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described: C:\Program Files\MySQL\MySQL Server 5.1\bin>mysqld --console --skip-grant-tables --innodb_buffer_pool_size=5G 100310 8:59:43 [Note] Plugin 'FEDERATED' is disabled. 100310 8:59:43 [ERROR] innobase_buffer_pool_size can't be over 4GB on 32-bit sy stems 100310 8:59:43 [ERROR] Plugin 'InnoDB' init function returned error. 100310 8:59:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 100310 8:59:43 [ERROR] Unknown/unsupported table type: INNODB 100310 8:59:43 [ERROR] Aborting 100310 8:59:43 [Note] mysqld: Shutdown complete
[2 Jul 2013 14:42]
Bugs System
Added a changelog entry for 5.7.2: "When the value provided for "innodb_buffer_pool_size" on 32-bit systems is too large, an error message would incorrectly reference the internal variable, "innobase_buffer_pool_size", instead of "innodb_buffer_pool_size"." Thank you for the bug report.