Skip to content

Commit 61d44e4

Browse files
author
github-actions
committed
update MD by dispatch event pingcap/docs release-8.1
1 parent 3ee7e41 commit 61d44e4

File tree

4 files changed

+12
-0
lines changed

4 files changed

+12
-0
lines changed

markdown-pages/en/tidb/release-8.1/information-schema/information-schema-tidb-index-usage.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,7 @@ The output is as follows:
101101

102102
- The data in the `TIDB_INDEX_USAGE` table might be delayed by up to 5 minutes.
103103
- After TiDB restarts, the data in the `TIDB_INDEX_USAGE` table is cleared.
104+
- TiDB records index usage for a table only when the table has valid statistics.
104105

105106
## Read more
106107

markdown-pages/en/tidb/release-8.1/ticdc/ticdc-ddl.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,7 @@ Assume that the configuration file of your changefeed is as follows:
118118
[filter]
119119
rules = ['test.t*']
120120

121+
[[filter.event-filters]]
121122
matcher = ["test.t1"] # This filter rule applies only to the t1 table in the test database.
122123
ignore-event = ["create table", "drop table", "truncate table", "rename table"]
123124
```

markdown-pages/en/tidbcloud/master/information-schema/information-schema-tidb-index-usage.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,7 @@ The output is as follows:
101101

102102
- The data in the `TIDB_INDEX_USAGE` table might be delayed by up to 5 minutes.
103103
- After TiDB restarts, the data in the `TIDB_INDEX_USAGE` table is cleared.
104+
- TiDB records index usage for a table only when the table has valid statistics.
104105

105106
## Read more
106107

markdown-pages/en/tidbcloud/master/tidb-cloud/backup-and-restore-serverless.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,15 @@ Create and restore to the new cluster. Note the following:
8080

8181
- User credentials and permissions from the source cluster will not be restored to the new cluster.
8282

83+
### Restore timeout
84+
85+
The restore process typically completes within a few minutes. If the restore takes longer than three hours, it is automatically canceled. The outcome of a canceled restore depends on the destination:
86+
87+
- **In-place restore**: the cluster status changes from **Restoring** to **Available**, and the cluster becomes accessible.
88+
- **Restore to a new cluster**: the new cluster is deleted and the source cluster remains unchanged.
89+
90+
If the data is corrupted after a canceled restore and cannot be recovered, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for assistance.
91+
8392
### Perform the restore
8493

8594
To restore your TiDB Cloud Serverless cluster, follow these steps:

0 commit comments

Comments
 (0)