Wrong transaction number in RDB$PAGES relation may cause infinite recusrion in engine and segfault [CORE5762] #6025
Labels
affect-version: 2.1.7
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2 Update 1
affect-version: 2.5.2
affect-version: 2.5.3 Update 1
affect-version: 2.5.3
affect-version: 2.5.4
affect-version: 2.5.5
affect-version: 2.5.6
affect-version: 2.5.7
affect-version: 2.5.8
affect-version: 3.0.0
affect-version: 3.0.1
affect-version: 3.0.2
affect-version: 3.0.3
affect-version: 4.0 Alpha 1
affect-version: 4.0 Initial
fix-version: 2.5.9
fix-version: 3.0.4
fix-version: 4.0 Beta 1
priority: major
qa: cannot be tested
type: bug
Submitted by: @AlexPeshkoff
Normally only system (i.e. zero) transaction updates RDB$PAGES relation. But due to:
- update by SYSDBA user (FB <3 only),
- database decryption error,
- generic data corruption
wrong transaction number can be read by engine for this table. Certainly all cases are more or less abnormal but segfault is not good diagnostic for it.
Commits: 3304a6d 2928eec 6e461ec
The text was updated successfully, but these errors were encountered: