mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 11:01:52 +01:00
39018f2a5a
Renamed suite/rpl/include/rpl_sync.inc to rpl_sync_test.inc to remove clash with include/rpl_sync.inc
32 lines
1.4 KiB
C++
32 lines
1.4 KiB
C++
#
|
|
# This include file is used by more than one test suite
|
|
# (currently rpl and binlog_encryption).
|
|
# Please check all dependent tests after modifying it
|
|
#
|
|
|
|
################################################################################
|
|
# Bug#19855907 IO THREAD AUTHENTICATION ISSUE WITH SOME CHARACTER SETS
|
|
# Problem: IO thread fails to connect to master if servers are configured with
|
|
# special character sets like utf16, utf32, ucs2.
|
|
#
|
|
# Analysis: MySQL server does not support few special character sets like
|
|
# utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
|
|
# When IO thread is trying to connect to Master, it sets server's character
|
|
# set as client's character set. When Slave server is started with these
|
|
# special character sets, IO thread (a connection to Master) fails because
|
|
# of the above said reason.
|
|
#
|
|
# Fix: If server's character set is not supported as client's character set,
|
|
# then set default's client character set(latin1) as client's character set.
|
|
###############################################################################
|
|
--source include/master-slave.inc
|
|
call mtr.add_suppression("'utf16' can not be used as client character set");
|
|
CREATE TABLE t1(i VARCHAR(20));
|
|
INSERT INTO t1 VALUES (0xFFFF);
|
|
--sync_slave_with_master
|
|
--let diff_tables=master:t1, slave:t1
|
|
--source include/diff_tables.inc
|
|
# Cleanup
|
|
--connection master
|
|
DROP TABLE t1;
|
|
--source include/rpl_end.inc
|