log_slow_verbosity set wrong in the code

Bug #987737 reported by Raghavendra D Prabhu on 2012-04-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Stewart Smith
Fix Released
Stewart Smith

Bug Description

Due to typo in the code, setting

log_slow_verbosity to profiling_use_getrusage (as documented here http://www.percona.com/doc/percona-server/5.1/diagnostics/slow_extended.html?id=percona-server:features:slow_extended_51&redirect=2#log_slow_verbosity) fails

Here is the patch:

--- sql/sys_vars.cc 2012-04-24 15:18:38.787681521 +0530
+++ /tmp/sys_vars.cc 2012-04-24 15:19:52.275679681 +0530
@@ -3077,7 +3077,7 @@
 const char* log_slow_verbosity_name[] = {
   "microtime", "query_plan", "innodb",
- "profiling", "profling_use_getrusage",
+ "profiling", "profiling_use_getrusage",
   "minimal", "standard", "full", 0
 static ulonglong update_log_slow_verbosity_replace(ulonglong value, ulonglong what, ulonglong by)

Workaround (till bug is fixed):

set [global] log_slow_verbosity=profling_use_getrusage;

Related branches

The exact error you get without fix is

set log_slow_verbosity=profiling_use_getrusage;
ERROR 1231 (42000): Variable 'log_slow_verbosity' can't be set to the value of 'profiling_use_getrusage'

set log_slow_verbosity=profling_use_getrusage;
Query OK, 0 rows affected (0.00 sec)

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1910

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers