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.

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

Lock Manager's ability to cancel wait shouldn't rely on engine internals [CORE3331] #3697

Open
firebird-automations opened this issue Feb 2, 2011 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Jira_subtask_inward CORE3323

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Initial implementation of improvement had no dependency on engine internals but requires changes in lock table structures which requires changing version number for lock table. It is bad for point release (2.5.1) but ok for major release (3.0). Currently another approach is investigated which requires no changes in lock table.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

summary: LM's ability to cancel wait shouldn't rely on engine internals => Lock Manager's ability to cancel wait shouldn't rely on engine internals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants