From 41fde07dff71498cec6017a10ff0576ddd4559ce Mon Sep 17 00:00:00 2001
From: TomShawn <1135243111@qq.com>
Date: Tue, 10 Mar 2020 17:35:29 +0800
Subject: [PATCH] reference/configuration: update note for stmt-count-limit in
 3.0/3.1

---
 reference/configuration/tidb-server/configuration-file.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reference/configuration/tidb-server/configuration-file.md b/reference/configuration/tidb-server/configuration-file.md
index bb4844f87d00f..6b56ddfd31764 100644
--- a/reference/configuration/tidb-server/configuration-file.md
+++ b/reference/configuration/tidb-server/configuration-file.md
@@ -211,7 +211,7 @@ Configuration items related to performance
 
 - The maximum number of statements allowed in a single TiDB transaction
 - Default value: `5000`
-- If a transaction does not roll back or commit after the number of statements exceeds `stmt-count-limit`, TiDB returns the `statement count 5001 exceeds the transaction limitation, autocommit = false` error.
+- If a transaction does not roll back or commit after the number of statements exceeds `stmt-count-limit`, TiDB returns the `statement count 5001 exceeds the transaction limitation, autocommit = false` error. This configuration takes effect **only** in the optimistic transaction. If you use the pessimistic transaction, the number of statements in a transaction is not limited by this configuration.
 
 ### `tcp-keep-alive`