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

Extend the transaction ID space beyond 2^32 transactions [CORE4965] #5256

Closed
firebird-issue-importer opened this issue Oct 19, 2015 · 7 comments
Closed

Comments

@firebird-issue-importer

Submitted by: @dyemanov

Relate to DNET896

Historically, transaction ID space was limited by 2^31 transactions (started since the database creation time). After that point, the database becomes unavailable until backup/restore is performed, which resets the transaction ID back to zero. Initial Firebird 3.0 version increased the transaction ID space to 2^32 transactions which doubles the database uptime without backup/restore.

This improvement request is about shifting that limit even further.

Firebird 3.0 RC1 introduces 48-bit internal transaction IDs that are publicly (via API and MON$ tables) represented as 64-bit numbers. This makes the new limit roughly equal to 2.8*10^14 transactions, later it could be extended up to the 2^63 limit. The implemented solution has no additional storage overhead until the transaction counters grow beyond the 2^32 boundary.

While being there, attachment IDs and statement IDs were changed to 64-bit numbers (both internally and externally).

Commits: 1ae6a9b 4e4d800 FirebirdSQL/fbt-repository@157dc9b FirebirdSQL/fbt-repository@4642bd0

====== Test Details ======

Database with Tx counters about 2.8*10^14 can not be prepared at reasonable time.
Direct updating of .fdb file (its TIP page) can lead to server crash after attempting to connect - so this ticket can not be tested by using fbtest.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 19, 2015

Modified by: @dyemanov

security: Managers [ 10013 ] =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 19, 2015

Modified by: @dyemanov

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 RC 1 [ 10584 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 19, 2015

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 20, 2015

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

Test Details: Database with Tx counters about 2.8*10^14 can not be prepared at reasonable time.
Direct updating of .fdb file (its TIP page) can lead to server crash after attempting to connect - so this ticket can not be tested by using fbtest.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 21, 2015

Modified by: @cincuranet

Link: This issue relate to DNET639 [ DNET639 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 5, 2019

Modified by: @cincuranet

Link: This issue relate to DNET639 [ DNET639 ] =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 13, 2019

Modified by: @cincuranet

Link: This issue relate to DNET896 [ DNET896 ]

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

Successfully merging a pull request may close this issue.

None yet
2 participants