Skip to content

Commit

Permalink
master/5.0: remove low-version descriptions (pingcap#5538)
Browse files Browse the repository at this point in the history
  • Loading branch information
Joyinqin authored Apr 29, 2021
1 parent d2d9e84 commit cf712bc
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 14 deletions.
2 changes: 0 additions & 2 deletions mysql-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,6 @@ However, some features of MySQL are not supported. This could be because there i

> **Note:**
>
> + To use the `tidb_allow_remove_auto_inc` system variable, your TiDB version must be >= v2.1.18 or >= v3.0.4.
> + The `AUTO_ID_CACHE` table attribute requires that your TiDB version >= v3.0.14 or >= v3.1.2 or >= v4.0.0-rc.2.
> + If you have not specified the primary key when creating a table, TiDB uses `_tidb_rowid` to identify the row. The allocation of this value shares an allocator with the auto-increment column (if such a column exists). If you specify an auto-increment column as the primary key, TiDB uses this column to identify the row. In this situation, the following situation might happen:
```sql
Expand Down
12 changes: 0 additions & 12 deletions tiflash/maintain-tiflash.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,18 +32,6 @@ There are two ways to check the TiFlash version:

## TiFlash critical logs

Starting from TiDB 4.0.5, TiFlash's log format has been refined for compatibility with TiDB. Therefore, there are two versions of log messages.
Before TiDB 4.0.5:
| Log Information | Log Description |
|---------------|-------------------|
| [ 23 ] `<Information>` KVStore: Start to persist [region 47, applied: term 6 index 10] | Data starts to be replicated (the number in the square brackets at the start of the log refers to the thread ID |
| [ 30 ] `<Debug>` CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request, that is, TiFlash starts to handle a Coprocessor request |
| [ 30 ] `<Debug>` CoprocessorHandler: grpc::Status DB::CoprocessorHandler::execute() | Handling DAG request done, that is, TiFlash finishes handling a Coprocessor request |
After TiDB 4.0.5:
| Log Information | Log Description |
|---------------|-------------------|
| [INFO] [`<unknown>`] ["KVStore: Start to persist [region 47, applied: term 6 index 10]"] [thread_id=23] | Data starts to be replicated (the number in the square brackets at the start of the log refers to the thread ID |
Expand Down

0 comments on commit cf712bc

Please sign in to comment.