cloud: add tidb-x-cloud.202603.1.md - #23458
Open
qiancai wants to merge 3 commits into
Open
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ti-chi-bot
Bot
added
missing-translation-status
|
Warning Review limit reached
Next review available in: 4 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded the TiDB-X-CLOUD.202603.1 release entry. The notes cover release metadata, performance, stability, observability, SQL, MySQL compatibility, parsing, query processing, optimizer behavior, and operational improvements. ChangesTiDB-X-CLOUD.202603.1 release documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: a5df0f53-536e-4885-8a72-138b176217e8
📒 Files selected for processing (1)
tidb-cloud/releases/tidb-x-cloud.202603.1.md
qiancai
commented
Aug 6, 2026
qiancai
commented
Aug 6, 2026
15 tasks
qiancai
commented
Aug 11, 2026
Comment on lines
+63
to
+69
| * Foreign key checks now support shared locks [#66154](https://github.com/pingcap/tidb/issues/66154) @[you06](https://github.com/you06) <!-- (dup): release-8.5.6.md > Features > Performance --> <!-- pr: https://github.com/pingcap/tidb/pull/69167, https://github.com/pingcap/tidb/pull/65752 --> | ||
|
|
||
| In pessimistic transactions, when you run `INSERT` or `UPDATE` on a child table with foreign key constraints, foreign key checks lock the corresponding parent table rows with exclusive locks by default. In high-concurrency write scenarios on the child table, if many transactions access the same parent table rows, severe lock contention can occur. | ||
|
|
||
| Now you can set the [`tidb_foreign_key_check_in_shared_lock`](https://docs.pingcap.com/tidb/v8.5/system-variables#tidb_foreign_key_check_in_shared_lock-new-in-v856) system variable to `ON` to let foreign key checks use shared locks on the parent table, thereby reducing lock contention and improving concurrent write performance on the child table. | ||
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/foreign-key#locking). |
Collaborator
Author
There was a problem hiding this comment.
Suggested change
| * Foreign key checks now support shared locks [#66154](https://github.com/pingcap/tidb/issues/66154) @[you06](https://github.com/you06) <!-- (dup): release-8.5.6.md > Features > Performance --> <!-- pr: https://github.com/pingcap/tidb/pull/69167, https://github.com/pingcap/tidb/pull/65752 --> | |
| In pessimistic transactions, when you run `INSERT` or `UPDATE` on a child table with foreign key constraints, foreign key checks lock the corresponding parent table rows with exclusive locks by default. In high-concurrency write scenarios on the child table, if many transactions access the same parent table rows, severe lock contention can occur. | |
| Now you can set the [`tidb_foreign_key_check_in_shared_lock`](https://docs.pingcap.com/tidb/v8.5/system-variables#tidb_foreign_key_check_in_shared_lock-new-in-v856) system variable to `ON` to let foreign key checks use shared locks on the parent table, thereby reducing lock contention and improving concurrent write performance on the child table. | |
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/foreign-key#locking). |
Collaborator
Author
There was a problem hiding this comment.
This feature is not ready for publishing yet.
qiancai
commented
Aug 11, 2026
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/optimizer-hints#index_lookup_pushdownt1_name-idx1_name--idx2_name--new-in-v855). | ||
|
|
||
| * Support table-level data affinity to improve query performance (experimental) [#9764](https://github.com/tikv/pd/issues/9764) @[lhy1024](https://github.com/lhy1024) <!-- (dup): release-8.5.5.md > Features > Performance --> <!-- pr: https://github.com/tikv/pd/pull/10157, https://github.com/tikv/pd/pull/10042, https://github.com/tikv/pd/pull/10103, https://github.com/tikv/pd/pull/10091, https://github.com/tikv/pd/pull/10080, https://github.com/tikv/pd/pull/10081, https://github.com/tikv/pd/pull/10043, https://github.com/tikv/pd/pull/10040, https://github.com/tikv/pd/pull/10041, https://github.com/tikv/pd/pull/10050, https://github.com/tikv/pd/pull/10038, https://github.com/tikv/pd/pull/9999, https://github.com/tikv/pd/pull/9998, https://github.com/tikv/pd/pull/9997, https://github.com/tikv/pd/pull/9993 --> |
|
|
qiancai
commented
Aug 19, 2026
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/sql-statement-select). | ||
|
|
||
| * Support partial indexes to reduce index storage and DML maintenance overhead [#62664](https://github.com/pingcap/tidb/issues/62664) [#62761](https://github.com/pingcap/tidb/issues/62761) [#62758](https://github.com/pingcap/tidb/issues/62758) [#63447](https://github.com/pingcap/tidb/issues/63447) [#64344](https://github.com/pingcap/tidb/issues/64344) @[YangKeao](https://github.com/YangKeao) @[winoros](https://github.com/winoros) @[wjhuang2016](https://github.com/wjhuang2016) <!-- (dup): release-8.5.7.md > Features > SQL --> <!-- miss issue https://github.com/pingcap/tidb/issues/63447 in release-8.5.7.md --> <!-- exclude author wjhuang2016 in release-8.5.7.md --> <!-- pr: https://github.com/pingcap/tidb/pull/64434, https://github.com/pingcap/tidb/pull/62762, https://github.com/pingcap/tidb/pull/62759, https://github.com/pingcap/tidb/pull/65051 --> |
qiancai
commented
Aug 19, 2026
|
|
||
| ### Performance | ||
|
|
||
| * Introduce significant performance improvements for certain lossy DDL operations (such as `BIGINT → INT` and `CHAR(120) → VARCHAR(60)`): when no data truncation occurs, the execution time of these operations can be reduced from hours to minutes, seconds, or even milliseconds, delivering performance gains ranging from tens to hundreds of thousands of times [#63366](https://github.com/pingcap/tidb/issues/63366) @[wjhuang2016](https://github.com/wjhuang2016), @[tangenta](https://github.com/tangenta), @[fzzf678](https://github.com/fzzf678) <!-- (dup): release-8.5.5.md > Features > Performance --> <!-- exclude author wjhuang2016 in release-8.5.5.md --> <!-- pr: https://github.com/pingcap/tidb/pull/64834, https://github.com/pingcap/tidb/pull/64337, https://github.com/pingcap/tidb/pull/64188, https://github.com/pingcap/tidb/pull/64111, https://github.com/pingcap/tidb/pull/63465, https://github.com/pingcap/tidb/pull/63970, https://github.com/pingcap/tidb/pull/63965 --> |
qiancai
commented
Aug 19, 2026
|
|
||
| Note that the preceding test results are based on the condition that no data truncation occurs during the DDL execution. The optimizations do not apply to conversions between signed and unsigned integer types, conversions between character sets, or tables with TiFlash replicas. | ||
|
|
||
| For more information, see [documentation](/sql-statements/sql-statement-modify-column.md). |
Collaborator
Author
There was a problem hiding this comment.
Suggested change
| For more information, see [documentation](/sql-statements/sql-statement-modify-column.md). | |
| For more information, see [documentation](https://docs.pingcap.com/tidb/v8.5/sql-statement-modify-column). |
qiancai
commented
Aug 19, 2026
|
|
||
| ### Observability | ||
|
|
||
| * Support defining multi-dimensional, fine-grained trigger rules for slow query logs [#62959](https://github.com/pingcap/tidb/issues/62959), [#64010](https://github.com/pingcap/tidb/issues/64010) @[zimulala](https://github.com/zimulala) <!-- (dup): release-8.5.6.md > Features > Observability --> <!-- miss issue https://github.com/pingcap/tidb/issues/64010 in release-8.5.6.md --> <!-- pr: https://github.com/pingcap/tidb/pull/66132, https://github.com/pingcap/tidb/pull/66064, https://github.com/pingcap/tidb/pull/65086 --> |
qiancai
commented
Aug 19, 2026
|
|
||
| ### SQL | ||
|
|
||
| * Support using table aliases in the `FOR UPDATE OF` clause [#63035](https://github.com/pingcap/tidb/issues/63035) @[cryo-zd](https://github.com/cryo-zd) <!-- (dup): release-8.5.6.md > Features > SQL --> <!-- pr: https://github.com/pingcap/tidb/pull/65532 --> |
qiancai
commented
Aug 19, 2026
|
|
||
| ### Stability | ||
|
|
||
| * The feature of setting the maximum limit on resource usage for background tasks of resource control becomes generally available (GA) [#56019](https://github.com/pingcap/tidb/issues/56019) @[glorv](https://github.com/glorv) <!-- (dup): release-8.5.6.md > Features > Stability --> <!-- pr: https://github.com/pingcap/tidb/pull/66381 --> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First-time contributors' checklist
What is changed, added or deleted? (Required)
Add tidb-x-cloud.202603.1.md
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit
LATERALsyntax parsing.FOR UPDATE OF.