*: remove tidb_batch_insert and tidb_batch_delete

dev/faq/tidb.md

@@ -940,11 +940,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. Therefore, it is not recommended to use this parameter in the production environment. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

dev/reference/configuration/tidb-server/tidb-specific-variables.md

@@ -166,27 +166,6 @@ set @@global.tidb_distsql_scan_concurrency = 10
 - This variable is used to set whether to skip UTF-8 validation.
 - Validating UTF-8 characters affects the performance. When you are sure that the input characters are valid UTF-8 characters, you can set the variable value to 1.
 
-### tidb_batch_insert
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the inserted data automatically. It is valid only when `autocommit` is enabled.
-- When inserting a large amount of data, you can set the variable value to `1`. Then, the inserted data is automatically divided into multiple batches and each batch is inserted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_batch_delete
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the data for deletion automatically. It is valid only when you delete from a single table and `autocommit` is enabled. For the definition of single-table DELETE statement, see [DELETE Syntax](https://dev.mysql.com/doc/refman/8.0/en/delete.html).
-- When deleting a large amount of data, you can set the variable value to `1`. Then, the data for deletion is automatically divided into multiple batches and each batch is deleted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_dml_batch_size
-
-- Scope: SESSION
-- Default value: 20000
-- This variable is used to set the automatically divided batch size of the data for insertion/deletion. It is only valid when `tidb_batch_insert` or `tidb_batch_delete` is enabled.
-- When the data size of a single row is very large, the overall data size of 20 thousand rows exceeds the size limit for a single transaction. In this case, set the variable to a smaller value.
-
 ### tidb_init_chunk_size
 
 - Scope: SESSION | GLOBAL

v1.0/FAQ.md

@@ -656,11 +656,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v2.0/FAQ.md

@@ -858,11 +858,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v2.1-legacy/FAQ.md

@@ -851,11 +851,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v2.1-legacy/sql/tidb-specific.md

@@ -150,27 +150,6 @@ set @@global.tidb_distsql_scan_concurrency = 10
 - This variable is used to set whether to skip UTF-8 validation.
 - Validating UTF-8 characters affects the performance. When you are sure that the input characters are valid UTF-8 characters, you can set the variable value to 1.
 
-### tidb_batch_insert
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the inserted data automatically. It is valid only when `autocommit` is enabled.
-- When inserting a large amount of data, you can set the variable value to true. Then the inserted data is automatically divided into multiple batches and each batch is inserted by a single transaction.
-
-### tidb_batch_delete
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the data for deletion automatically. It is valid only when `autocommit` is enabled.
-- When deleting a large amount of data, you can set the variable value to true. Then the data for deletion is automatically divided into multiple batches and each batch is deleted by a single transaction.
-
-### tidb_dml_batch_size
-
-- Scope: SESSION
-- Default value: 20000
-- This variable is used to set the automatically divided batch size of the data for insertion/deletion. It is only valid when `tidb_batch_insert` or `tidb_batch_delete` is enabled.
-- When the data size of a single row is very large, the overall data size of 20 thousand rows exceeds the size limit for a single transaction. In this case, set the variable to a smaller value.
-
 ### tidb_max_chunk_size
 
 - Scope: SESSION | GLOBAL

v2.1/faq/tidb.md

@@ -943,11 +943,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. Therefore, it is not recommended to use this parameter in the production environment. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v2.1/reference/configuration/tidb-server/tidb-specific-variables.md

@@ -150,27 +150,6 @@ set @@global.tidb_distsql_scan_concurrency = 10
 - This variable is used to set whether to skip UTF-8 validation.
 - Validating UTF-8 characters affects the performance. When you are sure that the input characters are valid UTF-8 characters, you can set the variable value to 1.
 
-### tidb_batch_insert
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the inserted data automatically. It is valid only when `autocommit` is enabled.
-- When inserting a large amount of data, you can set the variable value to `1`. Then, the inserted data is automatically divided into multiple batches and each batch is inserted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_batch_delete
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the data for deletion automatically. It is valid only when you delete from a single table and `autocommit` is enabled. For the definition of single-table DELETE statement, see [DELETE Syntax](https://dev.mysql.com/doc/refman/8.0/en/delete.html).
-- When deleting a large amount of data, you can set the variable value to `1`. Then, the data for deletion is automatically divided into multiple batches and each batch is deleted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_dml_batch_size
-
-- Scope: SESSION
-- Default value: 20000
-- This variable is used to set the automatically divided batch size of the data for insertion/deletion. It is only valid when `tidb_batch_insert` or `tidb_batch_delete` is enabled.
-- When the data size of a single row is very large, the overall data size of 20 thousand rows exceeds the size limit for a single transaction. In this case, set the variable to a smaller value.
-
 ### tidb_max_chunk_size
 
 - Scope: SESSION | GLOBAL

v3.0/faq/tidb.md

@@ -942,11 +942,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. Therefore, it is not recommended to use this parameter in the production environment. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v3.0/reference/configuration/tidb-server/tidb-specific-variables.md

@@ -166,27 +166,6 @@ set @@global.tidb_distsql_scan_concurrency = 10
 - This variable is used to set whether to skip UTF-8 validation.
 - Validating UTF-8 characters affects the performance. When you are sure that the input characters are valid UTF-8 characters, you can set the variable value to 1.
 
-### tidb_batch_insert
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the inserted data automatically. It is valid only when `autocommit` is enabled.
-- When inserting a large amount of data, you can set the variable value to `1`. Then, the inserted data is automatically divided into multiple batches and each batch is inserted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_batch_delete
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the data for deletion automatically. It is valid only when you delete from a single table and `autocommit` is enabled. For the definition of single-table DELETE statement, see [DELETE Syntax](https://dev.mysql.com/doc/refman/8.0/en/delete.html).
-- When deleting a large amount of data, you can set the variable value to `1`. Then, the data for deletion is automatically divided into multiple batches and each batch is deleted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_dml_batch_size
-
-- Scope: SESSION
-- Default value: 20000
-- This variable is used to set the automatically divided batch size of the data for insertion/deletion. It is only valid when `tidb_batch_insert` or `tidb_batch_delete` is enabled.
-- When the data size of a single row is very large, the overall data size of 20 thousand rows exceeds the size limit for a single transaction. In this case, set the variable to a smaller value.
-
 ### tidb_init_chunk_size
 
 - Scope: SESSION | GLOBAL

v3.1/faq/tidb.md

@@ -941,11 +941,7 @@ There are [similar limits](https://cloud.google.com/spanner/docs/limits) on Goog
 
 #### How to import data in batches?
 
-1. When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
-
-2. As for `insert` and `select`, you can open the hidden parameter `set @@session.tidb_batch_insert=1;`, and `insert` will execute large transactions in batches. In this way, you can avoid the timeout caused by large transactions, but this may lead to the loss of atomicity. Therefore, it is not recommended to use this parameter in the production environment. An error in the process of execution leads to partly inserted transaction. Therefore, use this parameter only when necessary, and use it in session to avoid affecting other statements. When the transaction is finished, use `set @@session.tidb_batch_insert=0` to close it.
-
-3. As for `delete` and `update`, you can use `limit` plus circulation to operate.
+When you import data, insert in batches and keep the number of rows within 10,000 for each batch.
 
 #### Does TiDB release space immediately after deleting data?
 

v3.1/reference/configuration/tidb-server/tidb-specific-variables.md

@@ -166,27 +166,6 @@ set @@global.tidb_distsql_scan_concurrency = 10
 - This variable is used to set whether to skip UTF-8 validation.
 - Validating UTF-8 characters affects the performance. When you are sure that the input characters are valid UTF-8 characters, you can set the variable value to 1.
 
-### tidb_batch_insert
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the inserted data automatically. It is valid only when `autocommit` is enabled.
-- When inserting a large amount of data, you can set the variable value to `1`. Then, the inserted data is automatically divided into multiple batches and each batch is inserted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_batch_delete
-
-- Scope: SESSION
-- Default value: 0
-- This variable is used to set whether to divide the data for deletion automatically. It is valid only when you delete from a single table and `autocommit` is enabled. For the definition of single-table DELETE statement, see [DELETE Syntax](https://dev.mysql.com/doc/refman/8.0/en/delete.html).
-- When deleting a large amount of data, you can set the variable value to `1`. Then, the data for deletion is automatically divided into multiple batches and each batch is deleted by a single transaction. This operation breaks the atomicity and isolation of the transaction. When performing this operation, you must ensure that there are **no other** ongoing operations on the table. When an error occurs, **manual intervention is required to check the consistency and integrity of the data**. Therefore, it is not recommended to set this variable in a production environment.
-
-### tidb_dml_batch_size
-
-- Scope: SESSION
-- Default value: 20000
-- This variable is used to set the automatically divided batch size of the data for insertion/deletion. It is only valid when `tidb_batch_insert` or `tidb_batch_delete` is enabled.
-- When the data size of a single row is very large, the overall data size of 20 thousand rows exceeds the size limit for a single transaction. In this case, set the variable to a smaller value.
-
 ### tidb_init_chunk_size
 
 - Scope: SESSION | GLOBAL