10bet网址
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr)- 36.3Mb
PDF (A4)- 36.3Mb
Man Pages (TGZ)- 235.6Kb
Man Pages (Zip)- 347.1Kb
Info (Gzip)- 3.3Mb
Info (Zip)- 3.3Mb
Excerpts from this Manual

5.4 MySQL Server Logs

MySQL Server has several logs that can help you find out what activity is taking place.

Log Type Information Written to Log
Error log Problems encountered starting, running, or stoppingmysqld
General query log Established client connections and statements received from clients
Binary log Statements that change data (also used for replication)
Relay log Data changes received from a replication source server
Slow query log Queries that took more thanlong_query_timeseconds to execute
DDL log (metadata log) Metadata operations performed by DDL statements

By default, no logs are enabled, except the error log on Windows. (The DDL log is always created when required, and has no user-configurable options; seeSection 5.4.6, “The DDL Log”.) The following log-specific sections provide information about the server options that enable logging.

By default, the server writes files for all enabled logs in the data directory. You can force the server to close and reopen the log files (or in some cases switch to a new log file) by flushing the logs. Log flushing occurs when you issue aFLUSH LOGSstatement; executemysqladminwith aflush-logsorrefreshargument; or executemysqldumpwith a--flush-logsor--master-dataoption. SeeSection 13.7.6.3, “FLUSH Statement”,Section 4.5.2, “mysqladmin — A MySQL Server Administration Program”, andSection 4.5.4, “mysqldump — A Database Backup Program”. In addition, the binary log is flushed when its size reaches the value of themax_binlog_sizesystem variable.

You can control the general query and slow query logs during runtime. You can enable or disable logging, or change the log file name. You can tell the server to write general query and slow query entries to log tables, log files, or both. For details, seeSection 5.4.1, “Selecting General Query Log and Slow Query Log Output Destinations”,5.4.3节“通用查询日志”, andSection 5.4.5, “The Slow Query Log”.

The relay log is used only on replicas, to hold data changes from the replication source server that must also be made on the replica. For discussion of relay log contents and configuration, seeSection 16.2.4.1, “The Relay Log”.

For information about log maintenance operations such as expiration of old log files, seeSection 5.4.7, “Server Log Maintenance”.

For information about keeping logs secure, seeSection 6.1.2.3, “Passwords and Logging”.