core: Expose next_tx_offset of the Replay decoder
#1899
Merged
Conversation
This file contains 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
Introduces a method on `Locking` to take a snapshot of the current committed state. Additionally a static method, so that the snapshot worker can use the same code. This is useful for tooling, where it usually does not make sense to spin up a `RelationalDB`.
Required by tooling to be able to iterate over transactions, starting from the offset after a (potential) snapshot restore.
This was referenced Oct 24, 2024
gefjon
approved these changes
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Required by tooling to be able to iterate over transactions, starting from the offset after a (potential) snapshot restore.
NOTE: On top of #1898, because the tooling work depends on the whole series.