89552

The setupobjects Table

The setup_objectstable Controls whether particular objects are monitored. This table

has a maximum size of 100 rows by default. The size may be changed by modifying the

performance_schema_setup_objects_size[2765] system variable at server startu p.

The initial setup_objectscontents look likethis:

mysql>SELECT * FROM setup_objects;

OBJECT	------+--------------- _TYPE | OBJECT_SCHEMA	-----+--- 1 OBJECT_	NAME 1	-----+----- 1 ENABLED |	-----+-------- 1 TIMED |
TABLE TABLE TABLE TABLE	1 mysąl | % | NO | NO 1 performance_schema | I information schema | I % | % | YES | YES | ------+---------------	1 % 1 NO 1 % | NO | -----+---	1 NO | 1 NO |	-----+-----	-----+--------

For object types listed in setup_objects, the Performance Schema uses the table to how to monitor

them. Object matching is based on the OBJECT_SCHEMA and OBJECT_NAME columns. Objects for

which there is no match are not monitored.

When the Performance Schema checks for a match in setup_objects, ittriesto find morę specific

matches first. For example, with a table dbl. 11, it looks for a match for ’dbl' and *tl', then for

'dbl' and ' % ', then for ' % ' and ' % '. The order in which matching occurs matters because different

setup_objectsrows can have different ENABLED and TIMED values.

The effect of the default object configuration is to instrument all tables except those in

the mysąl, IN FORMAT ION_SCH EMA, and per formance_schemadatabases. Tables in

the IN FORMAT ION_SCH EMA database are not instrumented regardless of the contents of

setup_objects; therowfor information_schema. % simply makes this default explicit.

The setup_objectstable has these columns:

•    OBJECT_TYPE

The type of object to instrument. Currently, this is ałways ' TABLE' (base table).

•    OBJECT_SCHEMA

The schema that contains the object. This should be a literał name, or * % ' to mean "any schema."