Consultation on Issues with the tidb_restricted_read_only Parameter During Transaction Operations

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb_restricted_read_only参数对事务操作时问题咨询

| username: xiaohetao

As shown in the blue part of the image:
If an uncommitted transaction has already made data changes, its commit will also be rejected.

Question: If the uncommitted data has already been changed, after the commit is rejected, is it enough for the transaction to roll back normally? Or is other action needed?

| username: xfworld | Original post link

This description indicates what the data was like before and will remain the same.

Before this parameter takes effect, if a transaction is started but not yet committed (at this time the parameter takes effect), the transaction commit will be rejected. I understand that the default transaction has expired (if the transaction expires, the lock will be cleared, and if it is not committed, the latest data will be provided for reading according to the previous state).

| username: xiaohetao | Original post link

The same as the transaction failure of the business.

| username: jansu-dev | Original post link


| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.