[TechDebt] Minor improvement to #8428 (Account for dictionary-building buffer in global memory limit) #9032
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.
Summary/Context:
cache_rev_mng
tocompression_dict_buffer_cache_res_mgr
cache_res_mgr
inBlockBasedTableBuilder
and to use correct short-hand for the words "reservation", "manager"table_options.block_cache == nullptr
in additional totable_options.no_block_cache == true
to be conditions where we don't create aCacheReservationManager
table_options.no_block_cache == true
is equivalent totable_options.block_cache == nullptr
by API. But since segment fault will be generated by passingnullptr
intoCacheReservationManager
's constructor, it does not hurt to directly verifytable_options.block_cache != nullptr
before passing inis_cache_full
toexceeds_global_block_cache_limit
Test: