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
Wrong index entries order at non-leaf b-tree pages [CORE1299] #1720
Comments
Commented by: @hvlad Edit database file name in both scripts. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0.2 [ 10130 ] => |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @hvladFix Version: 2.0.2 [ 10130 ] |
Modified by: @pcisarWorkflow: jira [ 12272 ] => Firebird [ 15600 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @hvlad
Relate to CORE1300
Is duplicated by CORE1616
Attachments:
CORE-1299.create_db.sql
CORE-1299.test_db.sql
Sometimes parent page contains nodes pointed at lower level pages in wrong order.
For example parent page nodes order A, B, C, D while at lower level pages linked in order A, C, B, D
This error can be detected by gfix. It reports in firebird.log 6 errors for the same index page for each such case :
(line number as per 2.0 sources)
This error itself can't lead to wrong query results, AFAIK, but i don't know if it can lead to more serious corruptions being present in actively modified index for a long time
Commits: ce54f65 512a33e
The text was updated successfully, but these errors were encountered: