Show information about SQL statement in the debug log about coprocessor encountering lock #27718
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
type/enhancement
The issue or PR belongs to an enhancement.
Enhancement
When coprocessor reading meets lock, TiDB will print a debug log. However it shows nothing about the related SQL statements, and there's not anywhere else that shows the statements that's affected by the lock. If this log can print the statement, it will be helpful for diagnose some problems. Of course, the statement in the log should be redacted according to the security options.
The text was updated successfully, but these errors were encountered: