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

internal Firebird consistency check (limbo impossible (184), file: vio.cpp line: 2379) [CORE5528] #5796

Closed
firebird-issue-importer opened this issue Apr 27, 2017 · 4 comments

Comments

@firebird-issue-importer

Submitted by: Gabor Boros (gaborboros)

Replaces CORE3679

https://groups.yahoo.com/neo/groups/firebird-support/conversations/messages/130762

Commits: 4d59428 e097468 6c5a2ae

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Apr 27, 2017

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Apr 28, 2017

Modified by: @hvlad

Link: This issue replaces CORE3679 [ CORE3679 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Apr 28, 2017

Commented by: @hvlad

There is no need for bugcheck, engine should handle in-limbo transactions in the same way at all places:
raise error or work as if transaction is active (if isc_tpb_ignore_limbo was specified).

Patch for V4 implements this strategy.

Patches for v2.5 and V3 still not check isc_tpb_ignore_limbo in prepare_update but now raises isc_rec_in_limbo
error instead of bugcheck, allowing all connections to continue work with database.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Apr 28, 2017

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 4.0 Alpha 1 [ 10731 ]

Fix Version: 3.0.3 [ 10810 ]

Fix Version: 2.5.8 [ 10809 ]

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