2.5.3.3 Test result Note: The following test results are the average data of three tests. All numbers are in seconds. Query ID TiDB v5.1 Greenplum 6.15.0 Apache Spark 3.1.1 + Parquet 1 8.08 64.1307 nodes that participates in the join operation, and sorts the nodes in the ascending order of row numbers. 588 Figure 64: join-reorder-1 After that, the table with the least rows is selected and joined second and the third query block, whose names are sel_2 and sel_3, respectively. The sequence of the numbers is based on the appearance of SELECT from left to right. If you replace the first SELECT with DELETE

DM code is migrated to the folder “dm” in TiCDC code repository. Now DM follows TiDB in version numbers. Next to v2.0.x, the new DM version is v5.3.0, and you can upgrade from v2.0.x to v5.3.0 without 2.5.3.3 Test result Note: The following test results are the average data of three tests. All numbers are in seconds. Query ID TiDB v5.3 Greenplum 6.15.0 Apache Spark 3.1.1 + Parquet 1 8.08 64.1307 nodes that participates in the join operation, and sorts the nodes in the ascending order of row numbers. 631 Figure 64: join-reorder-1 After that, the table with the least rows is selected and joined

2.5.3.3 Test result Note: The following test results are the average data of three tests. All numbers are in seconds. Query ID TiDB v5.2 Greenplum 6.15.0 Apache Spark 3.1.1 + Parquet 1 8.08 64.1307 nodes that participates in the join operation, and sorts the nodes in the ascending order of row numbers. 607 Figure 64: join-reorder-1 After that, the table with the least rows is selected and joined second and the third query block, whose names are sel_2 and sel_3, respectively. The sequence of the numbers is based on the appearance of SELECT from left to right. If you replace the first SELECT with DELETE

changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead efficiency. • It is recommended to enable the supportBigNumbers: true option when dealing with big numbers (BIGINT and DECIMAL columns) in the database. • It is recommended to enable the enableKeepAlive:

changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead efficiency. • It is recommended to enable the supportBigNumbers: true option when dealing with big numbers (BIGINT and DECIMAL columns) in the database. • It is recommended to enable the enableKeepAlive:

and stability during node restarts, cluster scaling-out, and network jitter when backing up large numbers of tables #52534 @3pointer • Implement fine-grained checks of TiCDC changefeed during data restore changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead

changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead efficiency. • It is recommended to enable the supportBigNumbers: true option when dealing with big numbers (BIGINT and DECIMAL columns) in the database. • It is recommended to enable the enableKeepAlive:

@zimulala Before v8.0.0, when you create a table, the default value of a column is limited to strings, numbers, dates, and certain expressions. Starting from v8.0.0, you can use more expressions as the default changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead

changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead efficiency. • It is recommended to enable the supportBigNumbers: true option when dealing with big numbers (BIGINT and DECIMAL columns) in the database. • It is recommended to enable the enableKeepAlive:

@zimulala Before v8.0.0, when you create a table, the default value of a column is limited to strings, numbers, dates, and certain expressions. Starting from v8.0.0, you can use more expressions as the default changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments. See Troubleshoot does not implement specific features deprecated in MySQL, including: • Specifying precision for floating-point types. MySQL 8.0 deprecates this feature, and it is recommended to use the DECIMAL type instead