[*] fix Reap() method to update Recovery cache after processing the previous value#815
Merged
pashagolub merged 1 commit intocybertec-postgresql:masterfrom Jun 24, 2025
Conversation
0xgouda
changed the title
Reap() method to update hostLastKnownStatuseInRecovery only after processing the previous valueReap() method to update Recovery cache after processing the previous value
Pull Request Test Coverage Report for Build 15848529645Details
💛 - Coveralls |
pashagolub
approved these changes
Jun 24, 2025
…ly after processing the previous value
pashagolub
force-pushed
the
fix-last-recovery-check
branch
from
7023102 to
8b1cbf4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
move the
hostLastKnownStatusInRecovery[monitoredSource.Name] = monitoredSource.IsInRecoveryupdate to after the processing of the last cached valuecloses: #814