You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug #29717909 MEMORY LIFETIME OF VARIABLES BETWEEN CHECK AND UPDATE INCORRECTLY MANAGED
Post push fix
1) innodb_buffer_pool_filename variable cannot be set to null in Windows. The behavior
is not consistent with Linux where there is no check function and it allows it be set
as NULL. It is better not to allow it to be set as NULL in Linux as well for the following reasons
(i) The purpose of the innodb_buffer_pool_filename is to specify the name of the file
where the list of tablespace IDs and page IDs produced by innodb_buffer_pool_dump_at_shutdown
or innodb_buffer_pool_dump_now should go.
(ii) When set as NULL in Linux and when we turn on innodb_buffer_pool_dump_now it creates a file called "(null)"
which is not correct.
So as a fix we will not allow innodb_buffer_pool_filename to be set as NULL
2) Doxygen failure in declaring the function name
Reviewed-by: Debarun Banerjee <debarun.banerjee@oracle.com>
0 commit comments