cloud: add tidb-x-cloud.202603.1.md - #23458
Open
qiancai wants to merge 15 commits into
Open
Conversation
ti-chi-bot
Bot
added
missing-translation-status
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review. 📝 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 Merge Risk: ⚪ Minimal · up to This change adds TiDB-X-CLOUD.202603.1 release documentation. No merge-blocking correctness or operational risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description includes the required template sections and identifies the added file, but it does not select the applicable TiDB version. The pull request targets the release-8.5 branch, so the v8.5 checkbox should be selected. ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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
14 tasks
qiancai
commented
Aug 11, 2026
|
|
qiancai
commented
Aug 19, 2026
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 --> |
qiancai
added
area/tidb-cloud
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
…ks of resource control
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
|
|
||
| Starting from v8.5.6, TiDB enhances slow query log control. You can use the [`tidb_slow_log_rules`](https://docs.pingcap.com/tidb/v8.5/system-variables#tidb_slow_log_rules-new-in-v856) system variable to define multi-dimensional slow query log output rules at the instance, session, and SQL levels, based on conditions such as `Query_time`, `Digest`, `Mem_max`, and `KV_total`. You can use [`tidb_slow_log_max_per_sec`](https://docs.pingcap.com/tidb/v8.5/system-variables#tidb_slow_log_max_per_sec-new-in-v856) to limit the number of log entries written per second, and use the [`WRITE_SLOW_LOG`](https://docs.pingcap.com/tidb/v8.5/optimizer-hints) hint to force slow query logging for specific SQL statements. This enables more flexible and fine-grained control over slow query logs. | ||
|
|
||
| For more information, see [documentation](https://docs.pingcap.com/tidbcloud/config-slow-query-trigger-rules/?plan=premium). |
Collaborator
Author
There was a problem hiding this comment.
Tip for reviewer: This above doc link will be available after https://github.com/pingcap/docs/pull/23767/files is merged.
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
qiancai
commented
Sep 8, 2026
| - Support partial ordered index optimization for `ORDER BY ... LIMIT/OFFSET` queries on matching prefix indexes. When `tidb_opt_partial_ordered_index_for_topn` is set to `COST`, TiDB can use the partial ordering of indexes to reduce full table scans and improve `TOPN` query performance [#63280](https://github.com/pingcap/tidb/issues/63280) [#65813](https://github.com/pingcap/tidb/issues/65813) [#66338](https://github.com/pingcap/tidb/issues/66338) @[elsa0520](https://github.com/elsa0520) @[xzhangxian1008](https://github.com/xzhangxian1008) @[winoros](https://github.com/winoros) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- miss issue https://github.com/pingcap/tidb/issues/66338 in release-8.5.7.md --> <!-- exclude author xzhangxian1008, winoros in release-8.5.7.md --> <!-- pr: https://github.com/pingcap/tidb/pull/65314, https://github.com/pingcap/tidb/pull/66268, https://github.com/pingcap/tidb/pull/66181, https://github.com/pingcap/tidb/pull/65799, https://github.com/pingcap/tidb/pull/65533 --> | ||
| - Mitigate coprocessor request bursts for `IndexLookUp` queries on highly partitioned tables with local indexes to improve query stability and reduce performance spikes [#67545](https://github.com/pingcap/tidb/issues/67545) @[gengliqi](https://github.com/gengliqi) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/69334 --> | ||
| - Optimize CPU and memory usage for `INSERT ... ON DUPLICATE KEY UPDATE` statements by reducing unnecessary expression buffer allocations during execution [#65003](https://github.com/pingcap/tidb/issues/65003) @[windtalker](https://github.com/windtalker) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/65244 --> | ||
| - Add the `tidb_opt_enable_alternative_logical_plans` system variable to enable alternative logical plan optimization for subquery decorrelation [#66676](https://github.com/pingcap/tidb/issues/66676) @[AilinKid](https://github.com/AilinKid) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/66677 --> |
qiancai
commented
Sep 8, 2026
| - Optimize CPU and memory usage for `INSERT ... ON DUPLICATE KEY UPDATE` statements by reducing unnecessary expression buffer allocations during execution [#65003](https://github.com/pingcap/tidb/issues/65003) @[windtalker](https://github.com/windtalker) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/65244 --> | ||
| - Add the `tidb_opt_enable_alternative_logical_plans` system variable to enable alternative logical plan optimization for subquery decorrelation [#66676](https://github.com/pingcap/tidb/issues/66676) @[AilinKid](https://github.com/AilinKid) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/66677 --> | ||
| - Optimize the logic for timestamp advancement and leader election [#9981](https://github.com/tikv/pd/issues/9981) @[bufferflies](https://github.com/bufferflies) <!-- (dup): release-8.5.5.md > Improvements > PD --> <!-- pr: https://github.com/tikv/pd/pull/9986 --> | ||
| - Support batch configuration of TiKV store limits by storage engine (TiKV or TiFlash) [#9970](https://github.com/tikv/pd/issues/9970) @[bufferflies](https://github.com/bufferflies) <!-- (dup): release-8.5.5.md > Improvements > PD --> <!-- pr: https://github.com/tikv/pd/pull/9978 --> |
qiancai
commented
Sep 8, 2026
| - Add the `tidb_opt_enable_alternative_logical_plans` system variable to enable alternative logical plan optimization for subquery decorrelation [#66676](https://github.com/pingcap/tidb/issues/66676) @[AilinKid](https://github.com/AilinKid) <!-- (dup): release-8.5.7.md > Improvements > TiDB --> <!-- pr: https://github.com/pingcap/tidb/pull/66677 --> | ||
| - Optimize the logic for timestamp advancement and leader election [#9981](https://github.com/tikv/pd/issues/9981) @[bufferflies](https://github.com/bufferflies) <!-- (dup): release-8.5.5.md > Improvements > PD --> <!-- pr: https://github.com/tikv/pd/pull/9986 --> | ||
| - Support batch configuration of TiKV store limits by storage engine (TiKV or TiFlash) [#9970](https://github.com/tikv/pd/issues/9970) @[bufferflies](https://github.com/bufferflies) <!-- (dup): release-8.5.5.md > Improvements > PD --> <!-- pr: https://github.com/tikv/pd/pull/9978 --> | ||
| - Add the `store` label to the `pd_cluster_status` metric [#9855](https://github.com/tikv/pd/issues/9855) @[SerjKol80](https://github.com/SerjKol80) <!-- (dup): release-8.5.5.md > Improvements > PD --> <!-- pr: https://github.com/tikv/pd/pull/9898 --> |
qiancai
commented
Sep 8, 2026
qiancai
added
translation/no-need
|
@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[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 |
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
4 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.