[External Buffer Manager] Step2: Abstracting away the atomic<idx_t> counter
#7053
+29
−23
Conversation
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
|
Thanks! LGTM |
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.
BufferPoolReservation now holds a reference to a BufferPool, instead of being fed an
atomic<idx_t> &counterin Resize.That also allows for BufferPool's that don't have an
atomic<idx_t>(such as the DummyBufferPool that the upcoming CBufferManager will use)This was a tweak that had to be done to be able to turn BufferManager into an interface, which is the next step.
But since that step is quite large, I thought it best to take these changes out of that PR