Help Center/
GaussDB(for MySQL)/
Troubleshooting/
Basic Issues/
No Scanned Rows Recorded in Slow Query Logs
Updated on 2023-10-19 GMT+08:00
No Scanned Rows Recorded in Slow Query Logs
Scenario
In slow query logs, an SQL statement was executed for 65 seconds, but the number of scanned rows was 0.
Possible Causes
If an SQL statement is interrupted but its execution time exceeds the slow log threshold, the statement will be recorded in slow query logs and the number of scanned rows is 0. Timeout thresholds have been configured for the JDBC connection from the client.
Solution
Optimize the SQL statement or set socketTimeout to an appropriate value.
Parent topic: Basic Issues
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
