log_slow_sp_statements interferes with log_slow_admin_statements
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
Medium
|
Nickolay Ihalainen | |||
5.6 |
Fix Released
|
Medium
|
Nickolay Ihalainen | |||
5.7 |
Fix Released
|
Medium
|
Nickolay Ihalainen |
Bug Description
When a stored routine calls an "administrative" command such as OPTIMIZE TABLE, ANALYZE TABLE, ALTER TABLE, CREATE/DROP INDEX, etc. the effective value of log_slow_
More specifically, mysql_execute_
As a result, with log_slow_
Conversely, with log_slow_
Steps to reproduce:
1. ./mysqld --log-slow-
2. create the following table and SP:
CREATE TABLE t1(a int);
delimiter //
CREATE PROCEDURE test() BEGIN INSERT INTO t1 VALUES(0); CREATE INDEX i ON t1(a); INSERT INTO t1 VALUES(1); END//
delimiter ;
3. in a debugger, set a breakpoint on log_slow_
4. execute "call test();"
5. log_slow_
description: | updated |
Changed in percona-server: | |
status: | New → Confirmed |
Changed in percona-server: | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in percona-server: | |
assignee: | nobody → Oleg Tsarev (tsarev) |
status: | Triaged → In Progress |
Changed in percona-server: | |
status: | In Progress → Triaged |
tags: | added: slow-extended |
Changed in percona-server: | |
assignee: | Oleg Tsarev (tsarev) → nobody |
https:/ /github. com/percona/ percona- server/ pull/597, https:/ /github. com/percona/ percona- server/ pull/1099, https:/ /github. com/percona/ percona- server/ pull/1100