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
AV with long inactive read-only read-commited transaction [CORE1657] #2081
Comments
Modified by: @AlexPeshkoff |
Commented by: @AlexPeshkoff Fix for CORE911 was incomplete. |
Modified by: @dyemanovdescription: Even after fix of core-911, a 'whole' in TIP cache between last time when read-only read-commited worked with database and current moment is possible, leadinf to AV when current transaction ID happens to be inside that 'whole'. => Even after fix of CORE911, a 'hole' in TIP cache between last time when read-only read-committed worked with database and current moment is possible, leading to AV when current transaction ID happens to be inside that 'hole'. |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 RC1 [ 10201 ] Fix Version: 2.0.4 [ 10211 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 13700 ] => Firebird [ 14107 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @AlexPeshkoff
Is related to CORE911
Even after fix of CORE911, a 'hole' in TIP cache between last time when read-only read-committed worked with database and current moment is possible, leading to AV when current transaction ID happens to be inside that 'hole'.
Commits: b531d60 ba90b5e
The text was updated successfully, but these errors were encountered: