:: DEVELOPER ZONE
MySQL Reference Manual :: 5.10 The MySQL Log Files
Search the MySQL manual:
- 5 Database Administration
- 5.1 The MySQL Server and Server Startup Scripts
- 5.2 The MySQL Instance Manager
- 5.3 Configuring the MySQL Server
- 5.4 The MySQL Server Shutdown Process
- 5.5 General Security Issues
- 5.6 The MySQL Access Privilege System
- 5.7 MySQL User Account Management
- 5.8 Disaster Prevention and Recovery
- 5.9 MySQL Localization and International Usage
- 5.10 The MySQL Log Files
- 5.11 Running Multiple MySQL Servers on the Same Machine
- 5.12 The MySQL Query Cache
Additional languages
Additional formats
MySQL has several different log files that can help you find out what's going on inside mysqld:
| Log File | Types of Information Logged to File |
| The error log | Logs problems encountered starting, running, or stopping mysqld. |
| The isam log |
Logs all changes to the ISAM tables. Used
only for debugging the isam code.
|
| The query log | Logs established client connections and executed statements. |
| The update log | Logs statements that change data. This log is deprecated. |
| The binary log | Logs all statements that change data. Also used for replication. |
| The slow log |
Logs all queries that took more than
long_query_time seconds to execute or
didn't use indexes.
|
By default, all logs are created in the mysqld
data directory. You can force mysqld to close and
reopen the log files (or in some cases switch to a new log) by
flushing the logs. Log flushing occurs when you issue a
FLUSH LOGS statement or execute
mysqladmin flush-logs or mysqladmin
refresh. See Section 13.5.5.2, “FLUSH Syntax”.
If you are using MySQL replication capabilities, slave replication servers maintain additional log files called relay logs. These are discussed in Chapter 6, Replication in MySQL.
© 1995-2005 MySQL AB. All rights reserved.
User Comments
Warning: query failed: Unknown column 'user.firstname' in 'field list' in /data0/sites/live/web-main/lib/mysql-cxn.php on line 69
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /data0/sites/live/web-main/lib/docbook.php on line 245
Add your own comment.