Last week, we published an article that goes over how to build and run your own TiDB or TiKV, and how to run some benchmarks on those databases. The full article is here:
TiDB 4.0 introduces SQL Plan Management (SPM), a mechanism that narrows down the optimizer's searching space to execution plans that are proven to perform well. SPM avoids performance degradation caused by unanticipated plan changes, and you don't have to change the application code.
Last week, we published an article that gives an overview of SPM and use an example to demonstrate how SPM helps the optimizer automatically select efficient execution plans.
The full article is here:
table not existerror code in release-3.0 is not the same as that in master
TestBuiltinunit test fails in different timezones
stmt_typein the statement summary