add v6.5.1 release notes #12809
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: dba3381 |
| - Fix the issue that when `globalMemoryControl` is killing a query, the `KILL` operation might not end [#41057](https://github.com/pingcap/tidb/issues/41057) @[wshwsh12](https://github.com/wshwsh12) | ||
| - Fix the issue that TiDB might panic after `indexMerge` encounters an error [#41047](https://github.com/pingcap/tidb/issues/41047) [#40877](https://github.com/pingcap/tidb/issues/40877) @[guo-shaoge](https://github.com/guo-shaoge) @[windtalker](https://github.com/windtalker) | ||
| - Fix the issue that the `ANALYZE` statement might be terminated by `KILL` [#41825](https://github.com/pingcap/tidb/issues/41825) @[XuHuaiyu](https://github.com/XuHuaiyu) | ||
| - Fix the issue that gorountine leak might occur in `indexMerge` [#41545](https://github.com/pingcap/tidb/issues/41545) [#41605](https://github.com/pingcap/tidb/issues/41605) @[guo-shaoge](https://github.com/guo-shaoge) |
There was a problem hiding this comment.
| - Fix the issue that gorountine leak might occur in `indexMerge` [#41545](https://github.com/pingcap/tidb/issues/41545) [#41605](https://github.com/pingcap/tidb/issues/41605) @[guo-shaoge](https://github.com/guo-shaoge) | |
| - Fix the issue that goroutine leak might occur in `indexMerge` [#41545](https://github.com/pingcap/tidb/issues/41545) [#41605](https://github.com/pingcap/tidb/issues/41605) @[guo-shaoge](https://github.com/guo-shaoge) |
|
In response to a cherrypick label: new pull request created to branch |
|
In response to a cherrypick label: new pull request created to branch |
* Create release-6.5.1.md * add 2 BR issues * Update release-6.5.1.md * replace with English existing release notes * update pr author for some issues * Update releases/release-6.5.1.md * Update release-6.5.1.md * Update release-6.5.1.md * Update releases/release-6.5.1.md * bug fix- tidb - first 13 * synch with Chinese changes * Apply suggestions from code review * Apply suggestions from code review Co-authored-by: xixirangrang <hfxsd@hotmail.com> * Update releases/release-6.5.1.md * Update releases/release-6.5.1.md Co-authored-by: xixirangrang <hfxsd@hotmail.com> * update TiDB, TiKV, and PD * Apply suggestions from code review Co-authored-by: Ran <huangran.alex@gmail.com> * Apply suggestions from code review Co-authored-by: Aolin <aolinz@outlook.com> * remove the dup mark * add v6.5.1 for TOC * Apply suggestions from code review * Apply suggestions from code review Co-authored-by: Grace Cai <qqzczy@126.com> * Update releases/release-6.5.1.md * Apply suggestions from code review Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> * Update releases/release-6.5.1.md * fix format * Update releases/release-6.5.1.md * fix anchor Signed-off-by: Ran <huangran.alex@gmail.com> --------- Signed-off-by: Ran <huangran.alex@gmail.com> Co-authored-by: qiancai <qqzczy@126.com> Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> Co-authored-by: xixirangrang <hfxsd@hotmail.com> Co-authored-by: Ran <huangran.alex@gmail.com> Co-authored-by: Aolin <aolinz@outlook.com> Co-authored-by: shichun-0415 <89768198+shichun-0415@users.noreply.github.com>
First-time contributors' checklist
What is changed, added or deleted? (Required)
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)?
Do your changes match any of the following descriptions?