SELECT WITH LOCK may raise unexpected update conflict errors under concurrent load [CORE5222] #5502
Assignees
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovreporter: Dmitry Yemanov [ dimitr ] => Gabor Boros [ gaborboros ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.1 [ 10730 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Gabor Boros (gaborboros)
This is a regression introduced in v3.0. Easily noticable in read-committed no-record-version mode.
Commits: 5f0842b 34399c1
The text was updated successfully, but these errors were encountered: