MySQL Bugs: #69766: InnoDB complains "There was a problem in converting <partition> in charset ...

Bug #69766	InnoDB complains "There was a problem in converting <partition> in charset ...
Submitted:	17 Jul 2013 17:08	Modified:	18 Jul 2013 12:23
Reporter:	Elena Stepanova	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.5.32	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
InnoDB prints messages like in the example below into the error log upon partition operations. I'm not sure what exactly it is trying to say, whether it is true or bogus, and if it is true, how dangerous it is, but at the very least the formatting is off, and the log looks ugly:

InnoDB: There was a problem in converting't1#P#p0' in charset filename to charset utf8_general_ciInnoDB: There was a problem in converting't1#P#p1' in charset filename to charset utf8_general_ci130717 19:56:42 [Note] /data/releases/mysql-5.5.32-linux2.6-x86_64/bin/mysqld: Normal shutdown

How to repeat:
create table t1 (pk int primary key) engine=InnoDB;
alter table t1 partition by hash(pk) partitions 2;
# check the error log

Hi!

I ran your test case , but was not able to repeat this neither by 5.5 or 5.6. Can you supply us with additional relevant info, like may be my.cnf file.

It is easily repeatable on 5.5.32 but not on latest bzr build.
Looking at the function innobase_convert_to_filename_charset we can see the fprintf has been removed.  So this is fixed already.

Given Shane's comment above, is my feedback still needed? 
I can't verify the top of the tree on obvious reasons, so if my confirmation is  required, it's going to have to wait till 5.5.33 is released or launchpad is updated, whichever comes first.

Elena,

No feedback needed from you.  This truly appears fixed in 5.5.33, so provide feedback only if the problem persists for you with 5.5.33.

Thanks a lot.