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

Database shutdown in Classic not forcing the release of External Table locks [CORE2476] #2889

Closed
firebird-automations opened this issue May 27, 2009 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Tim Barber (tim.barber)

If a session has an open transaction involving an external table, the external table is correctly locked.
However if gfix is used to shutdown the database, the lock remains until the session is used and the disconnect is detected by the client.
Gfix was used with the "-shut full -force 0" parameters.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

This is as designed - shutdown not breaks existing connections it just disallow any operation except of disconnect. I.e. client must disconnect by itself.

This behavior of shutdown could be changed in one of next release.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Vlad Khorsun [ hvlad ] => Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 2 [ 10300 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

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