| 1 |
# |
| 2 |
# This include file is used by more than one test suite |
| 3 |
# (currently rpl and binlog_encryption). |
| 4 |
# Please check all dependent tests after modifying it |
| 5 |
# |
| 6 |
|
| 7 |
################################################################################ |
| 8 |
# Bug#19855907 IO THREAD AUTHENTICATION ISSUE WITH SOME CHARACTER SETS |
| 9 |
# Problem: IO thread fails to connect to master if servers are configured with |
| 10 |
# special character sets like utf16, utf32, ucs2. |
| 11 |
# |
| 12 |
# Analysis: MySQL server does not support few special character sets like |
| 13 |
# utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2). |
| 14 |
# When IO thread is trying to connect to Master, it sets server's character |
| 15 |
# set as client's character set. When Slave server is started with these |
| 16 |
# special character sets, IO thread (a connection to Master) fails because |
| 17 |
# of the above said reason. |
| 18 |
# |
| 19 |
# Fix: If server's character set is not supported as client's character set, |
| 20 |
# then set default's client character set(latin1) as client's character set. |
| 21 |
############################################################################### |
| 22 |
--source include/master-slave.inc |
| 23 |
call mtr.add_suppression("'utf16' can not be used as client character set"); |
| 24 |
CREATE TABLE t1(i VARCHAR(20)) CHARSET=latin1; |
| 25 |
INSERT INTO t1 VALUES (0xFFFF); |
| 26 |
--sync_slave_with_master |
| 27 |
--let diff_tables=master:t1, slave:t1 |
| 28 |
--source include/diff_tables.inc |
| 29 |
# Cleanup |
| 30 |
--connection master |
| 31 |
DROP TABLE t1; |
| 32 |
--source include/rpl_end.inc |