Database validation reports false errors "Record XXX has bad transaction" and\or "Record XXX is wrong length" when record transaction number is greater than 2^32 [CORE5872] #6131
Assignees
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] Fix Version: 3.0.4 [ 10863 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested Test Details: It is not big problem to open fdb file and write into its header needed big values for Tx counters. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
firebird-automations
added
affect-version: 3.0.3
affect-version: 4.0 Alpha 1
affect-version: 3.0.2
affect-version: 3.0.1
affect-version: 3.0.0
affect-version: 4.0 Initial
fix-version: 4.0 Beta 1
fix-version: 3.0.4
resolution: fixed
priority: major
component: engine
type: bug
qa: cannot be tested
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @hvlad
Commits: 2d2bb74 709a48e
====== Test Details ======
It is not big problem to open fdb file and write into its header needed big values for Tx counters.
The real difficulty is to create multiple pages with type = TIP, with filling them and also to add references to them in RDB$PAGES (one *need* to create such pages otherwise bugcheck "cannot find tip page (165)" will raise).
This task looks impracticable, at least for nowadays.
The text was updated successfully, but these errors were encountered: