· · · · · · · · · · · · · · · 2502 13.14.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 2510 13.14.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · Configuration file Configuration Change type Description TiDBlower �→ - �→ case �→ - �→ table �→ - �→ names �→ DeletedCurrently TiDB only sup- ports lower_case_table_name �→ =2 �→ . If an- other value is set NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO �→ ,NO_ENGINE_SUBSTITUTION. • Default value of lower_case_table_names: • The default value in TiDB is 2 and currently TiDB only supports 2. • The default value in MySQL:

· · · · · · · · · · · · · · · 2846 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 2855 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · of lower_case_table_names: • The default value in TiDB is 2 and currently TiDB only supports 2. • The default value in MySQL: • On Linux: 0. It means that table and database names are stored on disk using table names are stored in lowercase on disk and name comparisons are not case-sensitive. MySQL converts all table names to lowercase on storage and lookup. This behavior also applies to database names and

· · · · · · · · · · · · · · · 3022 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3030 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on case-sensitive. • On Windows: 1. It means table names are stored in lowercase on disk, and name comparisons are not case-sensitive. MySQL converts all table names to lowercase on storage and lookup. This behavior

· · · · · · · · · · · · · · · 2954 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 2962 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · ANALYZE TABLE after reorganizing partitions #42183 @CbcWestwolf • Fix the issue of missing table names in the ADMIN SHOW DDL JOBS result when a DROP TABLE operation is being executed #42268 @tiancaiamao lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. 101 • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored

· · · · · · · · · · · · · · · 3010 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3018 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · Changes the default value from true to false after further tests, which means that the table names and database names in the TiCDC configu- ration file are case- insensitive by default. 52 Configuration file lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on

· · · · · · · · · · · · · · · 3211 13.11.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3220 13.11.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · tasks. PD cert- �→ allowed �→ -cn Modified Starting from v8.4.0, configur- ing multiple Common �→ Names �→ is sup- ported. Before v8.4.0, only one Common �→ Name can be set. 73 Configuration file or compo- lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on

· · · · · · · · · · · · · · · 3195 13.12.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3204 13.12.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · tasks. PD cert- �→ allowed �→ -cn Modified Starting from v8.4.0, configur- ing multiple Common �→ Names �→ is sup- ported. Before v8.4.0, only one Common �→ Name can be set. 68 Configuration file or compo- lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on

· · · · · · · · · · · · · · · 1856 11.12.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 1864 11.12.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · log-level, log-format, log-file, log- �→ rotation �→ -size Modified The names of TiKV log parameters are replaced with the names that are consistent with TiDB log parameters, which are log.level, log.format and TiKV Server start using a unified naming method for the log-related parameters to manage log names, output formats, and the rules for rotation and expiration. For details, see TiKV configuration file

· · · · · · · · · · · · · · · 3174 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3183 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on case-sensitive. • On Windows: 1. It means table names are stored in lowercase on disk, and name comparisons are not case-sensitive. MySQL converts all table names to lowercase on storage and lookup. This behavior

· · · · · · · · · · · · · · · 3142 13.13.2 Data Check for Tables with Different Schema or Table Names · · · · · · · · 3151 13.13.3 Data Check in the Sharding Scenario · · · · · · · · · · · · · · · · �→ allowed �→ - �→ user Newly added Lists the user- names that are allowed for client authenti- cation. Authen- tication requests with user- names not in this list will be rejected. The default value lower_case_table_names: • The default value in TiDB is 2, and only 2 is currently supported. • MySQL defaults to the following values: • On Linux: 0. It means that table and database names are stored on