diff --git a/pessimistic-transaction.md b/pessimistic-transaction.md
index 0e70754e59a61..0f561676891a8 100644
--- a/pessimistic-transaction.md
+++ b/pessimistic-transaction.md
@@ -79,6 +79,10 @@ Pessimistic transactions in TiDB behave similarly to those in MySQL. See the min
 
 - If the `Point Get` and `Batch Point Get` operators do not read data, they still lock the given primary key or unique key, which blocks other transactions from locking or writing data to the same primary key or unique key.
 
+    > **Note:**
+    >
+    > This behavior applies only to the [Repeatable Read](/transaction-isolation-levels.md#repeatable-read-isolation-level) isolation level. Under the [Read Committed](/transaction-isolation-levels.md#read-committed-isolation-level) isolation level, `Point Get` and `Batch Point Get` operators do not lock non-existent keys.
+
 - TiDB supports the `FOR UPDATE OF TABLES` syntax. For a statement that joins multiple tables, TiDB only applies pessimistic locks on the rows that are associated with the tables in `OF TABLES`.
 
 ## Differences from MySQL InnoDB