TiDB - v6.3.0

Improvements

• TiDB is now case-insensitive to the target table name when checking the table existence #34610 @tiancaiamao
• Improve MySQL compatibility by adding a parsing check when setting the value of init_connect #35324 @CbcWestwolf
• Improve the log warning generated for new connections #34964 @xiongjiwei
• Optimize the HTTP API for querying DDL history jobs, and add support for the start_job_id parameter #35838 @tiancaiamao
• Report errors when the JSON path has wrong syntax #22525 #34959 @xiongjiwei
• Improve the performance of Join operations by fixing a false sharing issue #37641 @gengliqi
• Support exporting the execution plan information of multiple SQL statements at a time using PLAN REPLAYER, which makes troubleshooting more efficient #37798 @Yisaer

Bug fixes

• Fix the issue that the privilege check is skipped for PREPARE statements #35784 @lcwangchao
• Fix the issue that the system variable tidb_enable_noop_variable can be set to WARN #36647 @lcwangchao
• Fix the issue that when an expression index is defined, the ORDINAL_POSITION column of the INFORMAITON_SCHEMA.COLUMNS table might be incorrect #31200 @bb7133
• Fix the issue that TiDB does not report an error when the timestamp is larger than MAXINT32 #31585 @bb7133
• Fix the issue that TiDB server cannot be started when the enterprise plugin is used #37319 @xhebox
• Fix the incorrect output of SHOW CREATE PLACEMENT POLICY #37526 @xhebox
• Fix the unexpected EXCHANGE PARTITION behaviors with temporary tables #37201 @lcwangchao
• Fix the issue that querying INFORMATION_SCHEMA.TIKV_REGION_STATUS returns an incorrect result @zimulala
• Fix the issue that the EXPLAIN query on views does not check privileges #34326 @hawkingrei
• Fix the issue that JSON null cannot be updated to NULL #37852 @YangKeao
• Fix the issue that row_count of DDL jobs is inaccurate #25968 @Defined2014
• Fix the issue that FLASHBACK TABLE does not work properly #37386 @tiancaiamao
• Fix the issue of failing to handle prepared statement flags in the typical MySQL protocol #36731 @dveeden
• Fix the issue of incorrect TiDB status that might appear on startup in some extreme cases #36791 @xhebox
• Fix the issue that INFORMATION_SCHEMA.VARIABLES_INFO does not comply with security enhanced mode (SEM) #37586 @CbcWestwolf
• Fix the issue that casting string to string goes wrong in queries with UNION #31678 @cbcwestwolf
• Fix the wrong result that occurs when enabling dynamic mode in partitioned tables for TiFlash #37254 @wshwsh12
• Fix the issue that the cast and comparison between binary strings and JSON in TiDB are incompatible with MySQL #31918 #25053 @YangKeao
• Fix the issue that JSON_OBJECTAGG and JSON_ARRAYAGG in TiDB are not compatible with MySQL on binary values #25053 @YangKeao
• Fix the issue that the comparison between JSON opaque values causes panic #37315 @YangKeao
• Fix the issue that the single precision float cannot be used in JSON aggregation funtions #37287 @YangKeao
• Fix the issue that the UNION operator might return unexpected empty result #36903 @tiancaiamao
• Fix the issue that the result of the castRealAsTime expression is inconsistent with MySQL #37462 @mengxin9014
• Fix the issue that pessimistic DML operations lock non-unique index keys #36235 @ekexium
• Fix the issue that auto-commit change affects transaction commit behaviours #36581 @cfzjywxk
• Fix the issue that the EXPLAIN ANALYZE statement with DML executors might return result before the transaction commit finishes #37373 @cfzjywxk
• Fix the issue that the UPDATE statements incorrectly eliminate the projection in some cases, which causes the Can't find column error #37568 @AilinKid
• Fix the issue that the Join Reorder operation will mistakenly push down its Outer Join condition #37238 @AilinKid
• Fix the issue that the IN and NOT IN subqueries in some patterns report the Can't find column error #37032 @AilinKid
• Fix the issue that Can't find column is reported if an UPDATE statement contains common table expressions (CTE) #35758 @AilinKid
• Fix incorrect PromQL #35856 @Defined2014