MySQL Bugs: #112042: The character set parameter (character_set

Bug #112042	The character set parameter (character_set_server) setting and packet capture re
Submitted:	11 Aug 2023 9:47	Modified:	14 Aug 2023 1:20
Reporter:	renqiang shen	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Server: Charsets	Severity:	S3 (Non-critical)
Version:	5.6.36	OS:	Linux (CentOS release 6.5)
Assigned to:		CPU Architecture:	x86

Description:
The global character set is set to utf8, the uri for client connections is set to utf8, and the character set settings for databases and tables are also set to utf8. However, the result of my packet capture shows server language: latin1

mysql> show session variables like 'char%';
+--------------------------+----------------------------------+
| Variable_name            | Value                            |
+--------------------------+----------------------------------+
| character_set_client     | utf8                             |
| character_set_connection | utf8                             |
| character_set_database   | utf8                             |
| character_set_filesystem | binary                           |
| character_set_results    | utf8                             |
| character_set_server     | utf8                             |
| character_set_system     | utf8                             |
| character_sets_dir       | /usr/local/mysql/share/charsets/ |
+--------------------------+----------------------------------+
mysql> show create table super_call.user\G
) ENGINE=InnoDB AUTO_INCREMENT=574152 DEFAULT CHARSET=utf8

The following are the results obtained through tcpdump：
Server Language: latin1 COLLATE latin1_swedish_ci (8)

How to repeat:
not repeat

This is the character set setting for client connections：
MySQL Protocol
    Packet Length: 245
    Packet Number: 1
    Login Request
        Client Capabilities: 0xa28f
        Extended Client Capabilities: 0x003a
        MAX Packet: 16777215
        Charset: utf8 COLLATE utf8_general_ci (33)

Hi Mr. shen,

Thank you for your bug report.

However, 5.6 is unsupported for the last 4 - 5 years. 

Processing and fixing bugs for 5.7 is ending next month. Hence, you should use latest 8.0 release. 

Read our Reference Manual on how to upgrade, step by step.

Unsupported.

Thank you for your letter. I will try upgrading the version to solve this problem

You are truly welcome ...