MySQL Bugs: #45922: Performance schema: LOCK_event_loop showing up in events though should not be

Bug #45922	Performance schema: LOCK_event_loop showing up in events though should not be
Submitted:	2 Jul 2009 20:50	Modified:	20 Jan 2014 9:29
Reporter:	Guilhem Bichot	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Performance Schema	Severity:	S3 (Non-critical)
Version:	6.0-perfschema	OS:	Linux
Assigned to:	Marc ALFF	CPU Architecture:	Any

Description:
I have: revision-id:marc.alff@sun.com-20090702000754-fnl3gfu1q3veoyg3
I modified suite/perfschema/t/pool_of_threads.test to be this:

--source include/not_embedded.inc
--source include/have_pool_of_threads.inc

update performance_schema.SETUP_INSTRUMENTS set enabled='NO', timed='NO';
update performance_schema.SETUP_CONSUMERS set enabled='YES';

truncate table performance_schema.EVENTS_WAITS_HISTORY_LONG;
 
select * from performance_schema.EVENTS_WAITS_HISTORY_LONG;

(I kept the master.opt file, to turn on thread-pooling). In the final SELECT I get:
THREAD_ID       EVENT_ID        EVENT_NAME      SOURCE  TIMER_START     TIMER_END       TIMER_WAIT      SPINS   OBJECT_SCHEMA   OBJECT_NAME     OBJECT_TYPE     OBJECT_INSTANCE_BEGIN   NESTING_EVENT_ID        OPERATION       NUMBER_OF_BYTES FLAGS
14      3       wait/synch/mutex/sql/LOCK_event_loop    scheduler.cc:626        177808657026    367489656534    189680999508    NULL    NULL    NULL    NULL    20934080        NULL    lock    NULL    0
LOCK_event_loop shows up, which I didn't expect as I previously set timed=enabled="NO" for all instruments...?

How to repeat:
use test above.

The pool-of-thread code is not part of 5.4.

Therefore, the pool_of_thread.test script (written for 6.0) has been removed from mysql-azalea-perfschema, since this test was always disabled in 5.4

Closing as can't repeat.

Upon request of the bug reporter,
changed to 'to be fixed later', where 'later' is the mysql version that
will contain instrumentation for the pool-of-thread implementation.

This version does not exists at this time.
The original test case can be found in mysql-6.0-perfschema.

There is no test named pool_of_thread in mysql-trunk on 5.6,
hence the bug report that starts with:
  "I modified suite/perfschema/t/pool_of_threads.test to ..."
can not be reproduced.

Beside, disabling setup_instruments has no effect on pending waits,
and only affect waits that will start after setup_instruments is modified,
so the original observation in the bug report is not conclusive.

Closing as not a bug.