Skip to content

Commit

Permalink
release note: add a check item for feedback-probability (pingcap#6405)
Browse files Browse the repository at this point in the history
  • Loading branch information
shichun-0415 authored and ti-chi-bot committed Sep 10, 2021
1 parent bdbf50b commit 57868cb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 0 deletions.
1 change: 1 addition & 0 deletions releases/release-5.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,7 @@ In v5.0, the key new features or improvements are as follows:

### Others

+ Before the upgrade, check the value of the TiDB configuration [`feedback-probability`](/tidb-configuration-file.md#feedback-probability). If the value is not 0, the "panic in the recoverable goroutine" error will occur after the upgrade, but this error does not affect the upgrade.
+ Forbid conversion between `VARCHAR` type and `CHAR` type during the column type change to avoid data correctness issues.

## New features
Expand Down
1 change: 1 addition & 0 deletions releases/release-5.1.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,7 @@ In v5.1, the key new features or improvements are as follows:

### Others

- Before the upgrade, check the value of the TiDB configuration [`feedback-probability`](/tidb-configuration-file.md#feedback-probability). If the value is not 0, the "panic in the recoverable goroutine" error will occur after the upgrade, but this error does not affect the upgrade.
- Upgrade the Go compiler version of TiDB from go1.13.7 to go1.16.4, which improves the TiDB performance. If you are a TiDB developer, upgrade your Go compiler version to ensure a smooth compilation.
- Avoid creating tables with clustered indexes in the cluster that uses TiDB Binlog during the TiDB rolling upgrade.
- Avoid executing statements like `alter table ... modify column` or `alter table ... change column` during the TiDB rolling upgrade.
Expand Down

0 comments on commit 57868cb

Please sign in to comment.