![]() |
MySQL 26.7.0
Source Code Documentation
|
#include <log0handler_interface.h>
Public Attributes | |
| bool | atomic_write |
| If true, then the implementation supports "atomic writes", which means that if any of the bytes passed to write_mtr(...) becomes available to read() then all of the bytes passed in this call are also available. More... | |
| bool | supports_clone |
| CLONE assumes direct access to files in specific location and format. More... | |
| bool | supports_meb |
| MEB assumes direct access to files in specific location and format. More... | |
| bool | supports_disabling |
| Is ALTER INSTANCE DISABLE INNODB REDO_LOG supported? More... | |
| bool | supports_encryption |
| True if REDO log encryption is supported. More... | |
| bool ib::redo::Handler_interface::Capabilities::atomic_write |
If true, then the implementation supports "atomic writes", which means that if any of the bytes passed to write_mtr(...) becomes available to read() then all of the bytes passed in this call are also available.
In other words it's impossible for the Log to appear to end abruptly in between of boundaries of chunks passed to write_mtr(...). Note that it doesn't mean that write_mtr(...) call itself must succeed, or persist the data immediately - it only means that IF and WHEN the data becomes available to read() it must do so in an atomic way. Contrast this with implementation which has atomic_write=false, which may cause a prefix of a buffer passed to write_mtr(...) to become available to the read() - say, due to OS deciding to flush part of the cache to disk and to crash immediately afterwards - forcing the client to carefully analyze data returned by read(..) to detect such unfinished writes.
| bool ib::redo::Handler_interface::Capabilities::supports_clone |
CLONE assumes direct access to files in specific location and format.
| bool ib::redo::Handler_interface::Capabilities::supports_disabling |
Is ALTER INSTANCE DISABLE INNODB REDO_LOG supported?
| bool ib::redo::Handler_interface::Capabilities::supports_encryption |
True if REDO log encryption is supported.
| bool ib::redo::Handler_interface::Capabilities::supports_meb |
MEB assumes direct access to files in specific location and format.