diff --git a/system-variables.md b/system-variables.md index acae3dffe6b0e..d736b0cac6381 100644 --- a/system-variables.md +++ b/system-variables.md @@ -1922,6 +1922,10 @@ Assume that you have a cluster with 4 TiDB nodes and multiple TiKV nodes. In thi > > The bulk DML execution mode (`tidb_dml_type = "bulk"`) is an experimental feature. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues). In the current version, when TiDB performs large transactions using the bulk DML mode, it might affect the memory usage and execution efficiency of TiCDC, TiFlash, and the resolved-ts module of TiKV, and might cause OOM issues. Additionally, BR might be blocked and fail to process when encountering locks. Therefore, it is not recommended to use this mode when these components or features are enabled. +> **Note:** +> +> This variable is read-only for [{{{ .starter }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#starter) and [{{{ .essential }}}](https://docs.pingcap.com/tidbcloud/select-cluster-tier#essential). + - Scope: SESSION - Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): Yes - Type: String diff --git a/tidb-cloud/limited-sql-features.md b/tidb-cloud/limited-sql-features.md index 3dddb34aed1ed..efa8101580cb6 100644 --- a/tidb-cloud/limited-sql-features.md +++ b/tidb-cloud/limited-sql-features.md @@ -142,6 +142,7 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som | `tidb_ddl_reorg_batch_size` | No limitation | Read-only [^10] | | `tidb_ddl_reorg_priority` | No limitation | Read-only [^10] | | `tidb_ddl_reorg_worker_cnt` | No limitation | Read-only [^10] | +| `tidb_dml_type` | No limitation | Read-only [^10] | | `tidb_enable_1pc` | No limitation | Read-only [^10] | | `tidb_enable_async_commit` | No limitation | Read-only [^10] | | `tidb_enable_auto_analyze` | No limitation | Read-only [^10] |