You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'.
description: 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'.
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: