Bug #79379: Inconsistent innodb_buffer_pool_size handling #45
Conversation
Remove code reserving extra bytes for the allocated memory block in buf_chunk_init(). Those extra bytes break the alignment even if the originally requested chunk is already properly aligned on all levels. That in turn results in all kinds of inconsistencies with large OS pages in setting innodb_buffer_pool_size both statically and dynamically.
akopytov
changed the title
|
Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment: |
|
I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it. |
|
Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow |
|
Is this still in the queue and not merged for 5.7.19, and thus http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.KnownIssuesAndLimitations.html still applies? |
|
@manuelkiessling Right, this has not been merged and is currently not available in any release series, not even in 8.0. |
|
Alright, thanks for the update! |
Run integration tests
Remove code reserving extra bytes for the allocated memory block in
buf_chunk_init(). Those extra bytes break the alignment even if the
originally requested chunk is already properly aligned on all
levels. That in turn results in all kinds of inconsistencies with large
OS pages in setting innodb_buffer_pool_size both statically and
dynamically.