-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SELECT LOCK IN SHARE MODE is unsafe #19383
Comments
/label sig/transaction |
This seems similar to #19506 -- I will take a look after it merges. |
Integrity check: |
Please edit this comment to complete the following informationBug1. Root Cause Analysis (RCA)The syntax 2. SymptomWhen using the syntax 3. All Trigger Conditionssee in Minimal reproduce step 4. Workaround (optional)The user can 5. Affected versions[v4.0.0:v4.0.99] 6. Fixed versionsunplaned |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
See: https://docs.pingcap.com/tidb/stable/pessimistic-transaction#difference-with-mysql-innodb
Under (2) it says that
SELECT LOCK IN SHARE MODE
is a noop. This seems unsafe, at least by default.2. What did you expect to see? (Required)
I would like to see it protected by the feature
tidb_enable_noop_functions
. This will allow users to explicitly turn it on, if they require syntax support but are fine with a noop.3. What did you see instead (Required)
The statement executes without errors.
4. What is your TiDB version? (Required)
All versions.
The text was updated successfully, but these errors were encountered: