From 07384190299f86f93027f416eece8d78b9dc4053 Mon Sep 17 00:00:00 2001 From: AmoebaProtozoa <8039876+AmoebaProtozoa@users.noreply.github.com> Date: Wed, 27 Nov 2024 16:30:09 +0800 Subject: [PATCH 1/3] update description Signed-off-by: AmoebaProtozoa <8039876+AmoebaProtozoa@users.noreply.github.com> --- system-variables.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/system-variables.md b/system-variables.md index 5122cfb03b933..739f713ccefcb 100644 --- a/system-variables.md +++ b/system-variables.md @@ -2840,16 +2840,12 @@ For a system upgraded to v5.0 from an earlier version, if you have not modified ### tidb_gc_life_time New in v5.0 -> **Note:** -> -> This variable is read-only for [TiDB Cloud Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-cloud-serverless). - - Scope: GLOBAL - Persists to cluster: Yes - Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No - Type: Duration - Default value: `10m0s` -- Range: `[10m0s, 8760h0m0s]` +- Range: `[10m0s, 8760h0m0s]` for TiDB Self-Managed and [TiDB Cloud Dedicated](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-cloud-dedicated), `[10m0s, 168h0m0s]` for [TiDB Cloud Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-cloud-serverless) - The time limit during which data is retained for each GC, in the format of Go Duration. When a GC happens, the current time minus this value is the safe point. > **Note:** From c2d73c0113d755eb43e9d65aeecd8cde1bd9e666 Mon Sep 17 00:00:00 2001 From: AmoebaProtozoa <8039876+AmoebaProtozoa@users.noreply.github.com> Date: Wed, 27 Nov 2024 16:33:49 +0800 Subject: [PATCH 2/3] update limited-sql-feature Signed-off-by: AmoebaProtozoa <8039876+AmoebaProtozoa@users.noreply.github.com> --- tidb-cloud/limited-sql-features.md | 1 - 1 file changed, 1 deletion(-) diff --git a/tidb-cloud/limited-sql-features.md b/tidb-cloud/limited-sql-features.md index 305e5802b5e1a..7963343377241 100644 --- a/tidb-cloud/limited-sql-features.md +++ b/tidb-cloud/limited-sql-features.md @@ -160,7 +160,6 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som | `tidb_force_priority` | Not supported [^4] | Not supported [^4] | | `tidb_gc_concurrency` | No limitation | Read-only [^10] | | `tidb_gc_enable` | No limitation | Read-only [^10] | -| `tidb_gc_life_time` | No limitation | Read-only [^10] | | `tidb_gc_max_wait_time` | No limitation | Read-only [^10] | | `tidb_gc_run_interval` | No limitation | Read-only [^10] | | `tidb_gc_scan_lock_mode` | No limitation | Read-only [^10] | From 2be43da102b7e7b28491ca8015c0167df6ac9edf Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 29 Nov 2024 23:00:31 +0800 Subject: [PATCH 3/3] Discard changes to tidb-cloud/limited-sql-features.md --- tidb-cloud/limited-sql-features.md | 1 + 1 file changed, 1 insertion(+) diff --git a/tidb-cloud/limited-sql-features.md b/tidb-cloud/limited-sql-features.md index 7963343377241..305e5802b5e1a 100644 --- a/tidb-cloud/limited-sql-features.md +++ b/tidb-cloud/limited-sql-features.md @@ -160,6 +160,7 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som | `tidb_force_priority` | Not supported [^4] | Not supported [^4] | | `tidb_gc_concurrency` | No limitation | Read-only [^10] | | `tidb_gc_enable` | No limitation | Read-only [^10] | +| `tidb_gc_life_time` | No limitation | Read-only [^10] | | `tidb_gc_max_wait_time` | No limitation | Read-only [^10] | | `tidb_gc_run_interval` | No limitation | Read-only [^10] | | `tidb_gc_scan_lock_mode` | No limitation | Read-only [^10] |