Permalink
Browse files

README, releases: add the release notes for 2.0.11 (#837)

  • Loading branch information...
CaitinChen committed Jan 3, 2019
1 parent 7ceccaa commit af0651af8fa91861da0faf42b727c9d224ea21f8
Showing with 23 additions and 0 deletions.
  1. +1 −0 README.md
  2. +21 −0 releases/2.0.11.md
  3. +1 −0 releases/rn.md
@@ -159,6 +159,7 @@
- [Frequently Asked Questions (FAQ)](FAQ.md)
- [TiDB Best Practices](https://pingcap.com/blog/2017-07-24-tidbbestpractice/)
+ [Releases](releases/rn.md)
- [2.0.11](releases/2.0.11.md)
- [2.1.2](releases/2.1.2.md)
- [2.0.10](releases/2.0.10.md)
- [2.1.1](releases/2.1.1.md)
@@ -0,0 +1,21 @@
---
title: TiDB 2.0.11 Release Notes
category: Releases
---

# TiDB 2.0.11 Release Notes

On January 03, 2019, TiDB 2.0.11 is released. The corresponding TiDB-Ansible 2.0.11 is also released. Compared with TiDB 2.0.10, this release has great improvement in system compatibility and stability.

## TiDB

- Fix the issue that the error is not handled properly when PD is in an abnormal condition [#8764](https://github.com/pingcap/tidb/pull/8764)
- Fix the issue that the `Rename` operation on a table in TiDB is not compatible with that in MySQL [#8809](https://github.com/pingcap/tidb/pull/8809)
- Fix the issue that the error message is wrongly reported when the `ADMIN CHECK TABLE` operation is performed in the process of executing the `ADD INDEX` statement [#8750](https://github.com/pingcap/tidb/pull/8750)
- Fix the issue that the prefix index range is incorrect in some cases [#8877](https://github.com/pingcap/tidb/pull/8877)
- Fix the panic issue of the `UPDATE` statement when columns are added in some cases [#8904](https://github.com/pingcap/tidb/pull/8904)

## TiKV

- Fix two issues about Region merge
[#4003](https://github.com/tikv/tikv/pull/4003), [#4004](https://github.com/tikv/tikv/pull/4004)
@@ -5,6 +5,7 @@ category: release

# TiDB Release Notes

- [2.0.11](../releases/2.0.11.md)
- [2.1.2](../releases/2.1.2.md)
- [2.0.10](../releases/2.0.10.md)
- [2.1.1](../releases/2.1.1.md)

0 comments on commit af0651a

Please sign in to comment.