Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Incorrect locking in READ_COMMITTED Isolation Mode #19

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Open

Incorrect locking in READ_COMMITTED Isolation Mode #19

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link
Collaborator 

In the NOT FOUND case, the lock on next key should be for instant duration
only. However, at present, the scan does not detect the NOT FOUND scenario,
and therefore cannot release the lock immediately. Only the calling client
can determine whether the key was found or not.

Original issue reported on code.google.com by [email protected] on 30 Dec 2007 at 2:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter