Bug #32573 Slow query Log is not much use for analysing Stored Procedures
Submitted: 21 Nov 2007 13:33 Modified: 21 Nov 2007 14:32
Reporter: Giles McArdell Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S4 (Feature request)
Version:5.0 OS:Any (All)
Assigned to: CPU Architecture:Any
Tags: slow query log, stored procedure
Triage: Triaged: D5 (Feature request)

[21 Nov 2007 13:33] Giles McArdell
Description:
When used to attempt to analyze stored procedures the Slow Query Log only reports the stored procedure name, not the actual statement causing the log entry.

In our process this is particularly useless as all our stored procedures are called in sequence from a 'wrapper' stored procedure so only the wrapper ever get reported in the log.

How to repeat:
switch on the slow query log and run some stored procedures.

Suggested fix:
In an ideal world the stored procedure name and the actual statement being run would appear in the Log.
[21 Nov 2007 14:32] Miguel Solorzano
Thank you for the feature request bug report.