Make remove_entry async in IDatabaseTransaction trait #964
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.
As a continuation of making the IDatabaseTransaction async, this PR makes remove_entry and rollback_to_savepoint async. This allows the executor to switch to a different thread in case some I/O is happening during remove_entry or rollback_to_savepoint.
I am only changing remove_entry and rollback_to_savepoint currently to keep the PR smaller and easier to review. The rest of the functions will be made async next.