The Error Log •Entries written to the log tables are not written to the binary log and thus are not replicated to replicas. •To flush the log tables or log files, use  FLUSH TABLES  or  FLUSH LOGS , respectively. •Partitioning of log tables is not permitted. •A  mysqldump  dump includes statements to recreate those tables so that they are not missing after reloading the dump file. Log table contents are not dumped. 5.4.2 The Error Log This section discusses how to configure the MySQL server for logging of diagnostic messages to the error log. For information about selecting the error message character set and language, see Section 10.6, “Error Message Character Set” , and Section 10.12, “Setting the Error Message Language” . The error log contains a record of  mysqld  startup and shutdown times. It also contains diagnostic messages such as errors, warnings, and notes that occur during server startup and shutdown, and while the server is running. For example, if  mysqld  notices that a table needs to be automatically checked or repaired, it writes a message to the error log. Depending on error log configuration, error messages may also populate the Performance Schema error_log  table, to provide an SQL interface to the log and enable its contents to be queried. See Section 27.12.21.1, “The error_log Table” . On some operating systems, the error log contains a stack trace if  mysqld  exits abnormally. The trace can be used to determine where  mysqld  exited. See Section 5.9, “Debugging MySQL” . If used to start  mysqld ,  mysqld_safe  may write messages to the error log. For example, when mysqld_safe  notices abnormal  mysqld  exits, it restarts  mysqld  and writes a  mysqld restarted message to the error log. The following sections discuss aspects of configuring error logging. In MySQL 8.0, error logging uses the MySQL component architecture described at Section 5.5, “MySQL Components” . The error log subsystem consists of components that perform log event filtering and writing, as well as a system variable that configures which components to enable to achieve the desired logging result. This section discusses how to select components for error logging. For instructions specific to log filters, see Section 5.4.2.4, “Types of Error Log Filtering” . For instructions specific to the JSON and system log sinks, see Section 5.4.2.7, “Error Logging in JSON Format” , and Section 5.4.2.8, “Error Logging to the System Log” . For additional details about all available log components, see Section 5.5.3, “Error Log Components” . Component-based error logging offers these features: •Log events can be filtered by filter components to affect the information available for writing. •Log events are output by sink (writer) components. Multiple sink components can be enabled, to write error log output to multiple destinations. •Built-in filter and sink components combine to implement the default error log format. •A loadable sink enables logging in JSON format. •A loadable sink enables logging to the system log. 1025 5.4.2.1 Error Log Configuration