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
The InnoDB log may be disabled by executing
SET GLOBAL innodb_log_file_disabled=ON;
in order to speed up any bulk operations, such as setting up a replica.
After the execution of
SET GLOBAL innodb_log_file_disabled=OFF;
has completed (and InnoDB has written a log checkpoint to the newly
enabled log), the server should be crash-safe again.
log_sys.buf_size_requested: The configured innodb_log_buffer_size.
While the log is disabled, we may set log_sys.buf_size (the actual size)
differently.
log_sys.disabled: The current setting of innodb_log_file_disabled.
log_t::attach(): Handle log_sys.disabled.
log_t::disabled(): Implements SET innodb_log_file_disabled=ON.
Even if the log used to be in persistent memory, here we will
set up dummy log_sys.buf and log_sys.flush_buf so that the dummy
writes will appear to use file based writes.
log_t::skip_write_buf(): A dummy log writer implementation that is
used when log_sys.disabled holds and the log is not being resized.
log_t::resize_start(): Handle log_sys.disabled, that is,
SET GLOBAL innodb_log_file_disabled=OFF when the redo log had
previously been disabled. If we are on persistent memory,
we will "fake" the dummy log_sys.buf to appear as memory-mapped
as well, so that log_t::resize_write() and log_t::resize_write_buf()
can assume that both log files are of the same type (memory-mapped
or file-based). The dummy log_sys.flush_buf will be stored in
log_sys.resize_flush_buf in that case.
0 commit comments