The order of results is different from MySQL when ORDER BY is omitted5251 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5253 26 15.3.8 Can the codec of TiDB In v8.4.0, TiDB improves the query performance of cached tables by up to 5.4 times when executing SELECT ... LIMIT 1 with IndexLookup. In addition, TiDB improves the performance of IndexLookupReader in 3 5.2 5.1 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y Y Y Y Y Y Y Y INSERT ON DUPLICATE KEY UPDATE Y Y Y Y Y Y Y Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y Y Y Y Y Y Y Y SELECT INTO OUTFILE Y Y

order of results is different from MySQL when ORDER BY is omitted5230 22 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5232 15.3.8 Can the codec of TiDB In v8.4.0, TiDB improves the query performance of cached tables by up to 5.4 times when executing SELECT ... LIMIT 1 with IndexLookup. In addition, TiDB improves the performance of IndexLookupReader in 3 5.2 5.1 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y Y Y Y Y Y Y Y INSERT ON DUPLICATE KEY UPDATE Y Y Y Y Y Y Y Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y Y Y Y Y Y Y Y SELECT INTO OUTFILE Y Y

The order of results is different from MySQL when ORDER BY is omitted5178 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5180 15.3.8 Can the codec of TiDB Support upgrading SELECT LOCK IN SHARE MODE to exclusive locks #54999 @cfzjywxk TiDB does not support SELECT LOCK IN SHARE MODE yet. Starting from v8.3.0, TiDB supports upgrading SELECT LOCK IN SHARE MODE MODE to exclusive locks to enable support for SELECT LOCK IN SHARE MODE. You can control whether to enable this feature by using the new system variable tidb_enable_shared_lock_promotion. For more information

The order of results is different from MySQL when ORDER BY is omitted5149 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5151 15.3.8 Can the codec of TiDB not supported error when you query TABLESAMPLE #54015 @tangenta • Fix the issue that executing the SELECT DISTINCT CAST(col AS DECIMAL), �→ CAST(col AS SIGNED)FROM ... query might return incorrect results issue that the TopN operator might be pushed down incorrectly #37986 @qw4990 • Fix the issue that SELECT INTO OUTFILE does not work when clustered indexes are used as predicates #42093 @qw4990 • Fix the

The order of results is different from MySQL when ORDER BY is omitted2346 13.2.3 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 2347 13.2.4 Can the codec of TiDB a specified time range. User document, #21094 The examples of AS OF TIMESTAMP are as follows: SELECT * FROM t AS OF TIMESTAMP '2020-09-06 00:00:00'; START TRANSACTION READ ONLY AS OF TIMESTAMP '2020-09-06 calculation of UNION ALL to solve the TiDB OOM problems when using UNION ALL to join a large number of SELECT statements #21441 – Optimize the dynamic pruning mode of partitioned tables to improve performance

The order of results is different from MySQL when ORDER BY is omitted5103 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 5105 15.3.8 Can the codec of TiDB Support the IMPORT INTO ... FROM SELECT syntax (GA) #49883 @D3Hunter Before v8.0.0, importing query results into a target table could only be done using the INSERT INTO ... SELECT statement, which is relatively scenarios. In v8.0.0, TiDB introduces IMPORT INTO ... FROM SELECT as an experimental feature, which enables you to import the results of a SELECT query into an empty TiDB target table. It achieves up to

The order of results is different from MySQL when ORDER BY is omitted2528 13.2.3 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 2530 13.2.4 Can the codec of TiDB statements 2 5.3 5.2 5.1 5.0 4.0 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y INSERT ON DUPLICATE KEY UPDATE Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y SELECT INTO OUTFILE Y Y Y Y Y INNER JOIN, LEFT\|RIGHT which ensures data consistency for each test. 5. Start the Sysbench client to perform the point_select, read_write, update_index, and update_non_index tests. Perform stress tests on TiDB via HAProxy.

The order of results is different from MySQL when ORDER BY is omitted2418 13.2.3 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 2419 13.2.4 Can the codec of TiDB improve query perfor- mance • Improve the accuracy of optimizer cardinality estimation to help to select optimal execution plans • Announce the general availability (GA) for the Lock View feature to observe queries on a large table that contain the order by col limit x con- dition, TiDB can more easily select the right index and reduce query response time. 36 – Improve the accuracy of out-of-range estimation

The order of results is different from MySQL when ORDER BY is omitted3866 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 3868 15.3.8 Can the codec of TiDB 3 5.2 5.1 5.0 4.0 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y Y Y Y INSERT ON DUPLICATE KEY �→ UPDATE Y Y Y Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y Y Y Y SELECT INTO OUTFILE Y Y Y Y Y Y Y which ensures data consistency for each test. 5. Start the Sysbench client to perform the point_select, read_write, update_index, and update_non_index tests. Perform stress tests on TiDB via HAProxy.

The order of results is different from MySQL when ORDER BY is omitted4878 15.3.7 Does TiDB support SELECT FOR UPDATE? · · · · · · · · · · · · · · · · · · · · · · · · · 4880 15.3.8 Can the codec of TiDB which saves your effort to create a binding for each database. CREATE GLOBAL BINDING FOR USING SELECT /*+ merge_join(t1, t2) */ t1.id, t2.amount FROM *.t1, *.t2 WHERE t1.id = t2.id; In addition, cross-database the convenience of creating execution plan bindings. For exam- ple: CREATE GLOBAL BINDING USING SELECT /*+ merge_join(t1, t2) */ * FROM t1, t2 WHERE t1.id = t2.id; 42 For more information, see documentation