innodb buf_resize_thread - release mutexes when no change #74
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.
The Innodb buf_resize_thread fails to release the mutexes when the old and new innodb buffer pool sizes are the same.
While the innodb_buffer_pool_size_validate does actually do the same check, its theoretically possible to resize the pool twice and trigger this condition if both changes occur before innodb_buffer_pool_size_update is called the first time.