log_slow_slave_statements doesn't work with log_slow_verbosity=innodb

Bug #600684 reported by Oleg Tsarev on 2010-07-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Oleg Tsarev

Bug Description

If we:

1) setup:
set long_query_time=0;
set log_slow_verbosity=innodb;
set global log_slow_slave_statements=ON;
on master and slave
2) restart slave thread (in other case log_slow_slave_statements doesn't affect)
3) run insert queries on master


# User@Host: [SQL_SLAVE] @ []
# Thread_id: 7 Schema: test Last_errno: 0 Killed: 0
# Query_time: 0.007577 Lock_time: 0.000050 Rows_sent: 0 Rows_examined: 930 Rows_affected: 900 Rows_read: 900
# Bytes_sent: 0 Tmp_tables: 1 Tmp_disk_tables: 0 Tmp_table_sizes: 126992
# No InnoDB statistics available for this query
SET timestamp=1277997479;
INSERT INTO t SELECT t2.id from t as t1, t as t2;

Insert queries replicated to slave doesn't have InnoDB stats in slow query


All queries replicated to slave and go to slow query log should include InnoDB stats, if we setup it.

Test attached (this not clear test, this only way for extract log with trouble)

Oleg Tsarev (tsarev) wrote :
Oleg Tsarev (tsarev) wrote :
Oleg Tsarev (tsarev) wrote :
Changed in percona-server:
assignee: nobody → Oleg Tsarev (tsarev)
importance: Undecided → Medium
milestone: none → 5.1-12.0
status: New → Triaged
Oleg Tsarev (tsarev) on 2010-07-01
Changed in percona-server:
status: Triaged → In Progress
Oleg Tsarev (tsarev) on 2010-07-06
Changed in percona-server:
status: In Progress → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released

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

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

Other bug subscribers