Bug #78036 MySQL slave breaks off when create/drop table using gbk/gb2313 charset

• Submitted: 12 Aug 2015 9:10
• Modified: 13 Aug 2015 6:05
• Reporter: Zhao Jianwei
• Status: Duplicate
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 5.5.18, 5.6.16, 5.6.26, 5.6.27
• OS: Linux
• CPU Architecture: Any

[12 Aug 2015 9:10] Zhao Jianwei

Description:
Hi，
  
   My environment is chinese, so we use 'gbk' as default charset. when I issued 'create/drop table table_name' which including chinese character in table_name,
MySQL master DBNode is ok, but slave faced such error:

Last_SQL_Errno  1051
Last_SQL_Error  Error 'Unknown table 't_闁瑰瓨鍨冲鎴︽儍閸銈撮悹鍥ㄦСhina'' on query. Default database: 'test'. Query: 'DROP TABLE `t_閹存婊戦惃鍕ゴ鐠囨槳hina` /* generated by server */'

Sorry for that you may see messy code。

How to repeat:
--source include/master-slave.inc

connection master;
set names gbk;
create table test.`t_鎴戜滑鐨
                             娴嬭瘯china`(id int);
use test;
show tables;
drop table test.`t_鎴戜滑鐨
                           娴嬭瘯china`;

sync_slave_with_master;

connection slave;
use test;
show tables;

--source include/rpl_end.inc

[12 Aug 2015 9:11] Zhao Jianwei

The testcase file。

Attachment: t.test (application/octet-stream, text), 288 bytes.

[12 Aug 2015 11:07] MySQL Verification Team

Hello Zhao,

Thank you for the report and test case.
Observed this with 5.6.26 and 5.6.27 builds.

Thanks,
Umesh

[12 Aug 2015 11:07] MySQL Verification Team

test results

Attachment: 78036.results (application/octet-stream, text), 28.97 KiB.

[13 Aug 2015 6:05] MySQL Verification Team

This is duplicate of Bug #77249