MySQL Bugs: #31675: GB values not honored in MySQL Administrator

Bug #31675	GB values not honored in MySQL Administrator
Submitted:	17 Oct 2007 20:38	Modified:	30 Nov 2009 16:17
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.2.12	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
The MySQL Administrator allows users to modify server startup parameters, altering the server configuration file.  However, many of these parameters are represented by two fields:  a text field for a numeric value, and a drop-down indicating whether the value is in KB or MB.  There is no option for GB, however, and there are parameters (such as innodb_buffer_pool_size) for which values of 1GB or greater are valid.  When these values exist in the configuration file and are parsed, they display as 1 KB instead of 1 GB.  While this doesn't update the values when other changes are made, if the drop-down is changed (to look for GB, for instance) and left at KB, the 1G entry in the configuration file is overwritten with 1k.

How to repeat:
Start server.  Edit configuration file to include:

innodb_buffer_pool_size=1G

Start MySQL Administrator.  Edit server startup variables.  Note that InnoDB Buffer Pool Size displays as 1k.

Suggested fix:
Add support for GB values in drop down, or parse GB values from config file into appropriate MB values.

same comment as here:
http://bugs.mysql.com/bug.php?id=31699

Many thanks Todd for pointing this out.

Also in actual version there is just K and M.

Because we are on the way to implement full functionality of MySQL Administrator into MySQL Workbench we won't implement this feature anymore.

Todd,

sorry, I first missunderstood.

This is already fixed.

Buffer Pool Size = 1024 M

It will displayed as 1024 M and not just as 1 K.

There is none G and because of Workbench implementation we won't add the G here. But I think it is ok to have 1024 M instead of 1 G.

Our actual version is MySQL Administrator 1.2.16. You will be able to download it here:

  http://www.mysql.com/downloads/

Sorry, I made a verification error here.

When you put in my.ini configure values with 2GB then they will shown as 2K in Administrator.

This not only hit innodb_buffer_pool. It hits some others as well. I didn't test all but it looks like all values where GB is possible are hit here.

Bug #31699 is another effect of this bug here. Bug 31699 is set as duplicate of this bug here because both behaviour have same root.

I cannot reproduce this problem. When I set a value of 2000M in the config file it shows up as this value. Once changed to 1024M this is saved to the config file and loaded next time I start MA. So, I don't see what to do here.

Use a value such as the following:

innodb_buffer_pool_size=1G

NOT

innodb_buffer_pool_size=1024M

Both are the same; MySQL Server parses both to have the same value, but MySQL Administrator displays the first as "1k".

It needs to be checked if this is working correct in Workbench 5.2. I will test it.

We won't fix this in Administrator anymore. But bug #49013 is the regression Workbench bug for this bug here.