The ENABLED  column indicates whether matching objects are monitored, and TIMED  indicates whether to collect timing information. Setting the TIMED  column affects Performance Schema table contents as described in Section 27.4.1, “Performance Schema Event Timing” . 

The effect of the default object configuration is to instrument all objects except those in the mysql , INFORMATION_SCHEMA , and performance_schema  databases. (Tables in the INFORMATION_SCHEMA database are not instrumented regardless of the contents of setup_objects ; the row for information_schema.%  simply makes this default explicit.) 

When the Performance Schema checks for a match in setup_objects , it tries to find more specific matches first. For rows that match a given OBJECT_TYPE , the Performance Schema checks rows in this order: 

•Rows with OBJECT_SCHEMA=’ literal ’  and OBJECT_NAME=’ literal ’ . 

•Rows with OBJECT_SCHEMA=’ literal ’  and OBJECT_NAME=’%’ . 

•Rows with OBJECT_SCHEMA=’%’  and OBJECT_NAME=’%’ . 

For example, with a table db1.t1 , the Performance Schema looks in TABLE  rows for a match for ’db1’ and ’t1’ , then for ’db1’  and ’%’ , then for ’%’  and ’%’ . The order in which matching occurs matters because different matching setup_objects  rows can have different ENABLED  and TIMED  values. 

For table-related events, the Performance Schema combines the contents of setup_objects  with setup_instruments  to determine whether to enable instruments and whether to time enabled instruments: 

•For tables that match a row in setup_objects , table instruments produce events only if ENABLED  is YES  in both setup_instruments  and setup_objects . 

•The TIMED  values in the two tables are combined, so that timing information is collected only when both values are YES . 

For stored program objects, the Performance Schema takes the ENABLED  and TIMED  columns directly from the setup_objects  row. There is no combining of values with setup_instruments . 

Suppose that setup_objects  contains the following TABLE  rows that apply to db1 , db2 , and db3 : 

+-------------+---------------+-------------+---------+-------+ | OBJECT_TYPE | OBJECT_SCHEMA | OBJECT_NAME | ENABLED | TIMED | +-------------+---------------+-------------+---------+-------+ | TABLE | db1 | t1 | YES | YES | | TABLE | db1 | t2 | NO | NO | | TABLE | db2 | % | YES | YES | | TABLE | db3 | % | NO | NO | | TABLE | % | % | YES | YES | +-------------+---------------+-------------+---------+-------+ 

If an object-related instrument in setup_instruments  has an ENABLED  value of NO , events for the object are not monitored. If the ENABLED  value is YES , event monitoring occurs according to the ENABLED  value in the relevant setup_objects  row: 

• db1.t1  events are monitored 

• db1.t2  events are not monitored 

• db2.t3  events are monitored 

• db3.t4  events are not monitored 

