MySQL Manual
4 Database Administration
- 4.1 Configuring MySQL
- 4.2 General Security Issues and the MySQL Access Privilege System
- 4.3 MySQL User Account Management
- 4.4 Disaster Prevention and Recovery
- 4.5 Database Administration Language Reference
- 4.6 MySQL Localisation and International Usage
- 4.7 MySQL Server-Side Scripts and Utilities
- 4.8 MySQL Client-Side Scripts and Utilities
- 4.9 The MySQL Log Files
- 4.10 Replication in MySQL
4.9 The MySQL Log Files
MySQL has several different log files that can help you find
out what's going on inside mysqld:
| Log file | Description |
| The error log | Problems encountering 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 | Established connections and executed queries. |
| The update log | Deprecated: Stores all statements that changes data |
| The binary log | Stores all statements that changes something. Used also for replication |
| The slow log | Stores all queries that took more than long_query_time seconds to execute or didn't use indexes.
|
All logs can be found in the mysqld data directory. You can
force mysqld to reopen the log files (or in some cases
switch to a new log) by executing FLUSH LOGS. See section 4.5.3 FLUSH Syntax.
Subsections
- 4.9.1 The Error Log
- 4.9.2 The General Query Log
- 4.9.3 The Update Log
- 4.9.4 The Binary Log
- 4.9.5 The Slow Query Log
- 4.9.6 Log File Maintenance
User Comments
| Posted by Brian Vicente on Wednesday July 16 2003, @2:44pm | [Delete] [Edit] |
Given that you have the logs(query,update,error). How does one go about linking thread to user:host:query?
