Performance Schema Statement Event Tables a  COM_QUERY  packet, it is known to correspond to an SQL statement but not the particular type of statement. In this case, the instrument changes from one abstract name to a more specific but still abstract name,  statement/abstract/Query , and the request requires further classification. For a request read as a statement from the relay log on a replica: The preceding description applies only for statement-based replication. For row-based replication, table I/ O done on the replica as it processes row changes can be instrumented, but row events in the relay log do not appear as discrete statements. For a request received from the Event Scheduler: The event execution is instrumented using the name  statement/scheduler/event . This is the final name. Statements executed within the event body are instrumented using  statement/sql/*  names, without use of any preceding abstract instrument. An event is a stored program, and stored programs are precompiled in memory before execution. Consequently, there is no parsing at runtime and the type of each statement is known by the time it executes. Statements executed within the event body are child statements. For example, if an event executes an  INSERT  statement, execution of the event itself is the parent, instrumented using  statement/ scheduler/event , and the  INSERT  is the child, instrumented using  statement/sql/insert . The parent/child relationship holds  between  separate instrumented operations. This differs from the sequence of refinement that occurs  within  a single instrumented operation, from abstract to final instrument names. For statistics to be collected for statements, it is not sufficient to enable only the final  statement/sql/* instruments used for individual statement types. The abtract  statement/abstract/*  instruments must be enabled as well. This should not normally be an issue because all statement instruments are enabled by default. However, an application that enables or disables statement instruments selectively must take into account that disabling abstract instruments also disables statistics collection for the individual statement instruments. For example, to collect statistics for  INSERT  statements,  statement/sql/ insert  must be enabled, but also  statement/abstract/new_packet  and  statement/abstract/ Query . Similarly, for replicated statements to be instrumented,  statement/abstract/relay_log  must be enabled. No statistics are aggregated for abstract instruments such as  statement/abstract/Query  because no statement is ever classified with an abstract instrument as the final statement name. The  events_statements_current  table contains current statement events. The table stores one row per thread showing the current status of the thread’s most recent monitored statement event, so there is no system variable for configuring the table size. 27.12.6.1 The events_statements_current Table 4973 3. If the request is a statement, the statement text is read and given to the parser. After parsing, the exact statement type is known. If the request is, for example, an  INSERT  statement, the Performance Schema refines the instrument name from  statement/abstract/Query  to  statement/sql/ insert , which is the final name. 1. Statements in the relay log are stored as text and are read as such. There is no network protocol, so the  statement/abstract/new_packet  instrument is not used. Instead, the initial instrument is statement/abstract/relay_log . 2. When the statement is parsed, the exact statement type is known. If the request is, for example, an  INSERT  statement, the Performance Schema refines the instrument name from  statement/ abstract/Query  to  statement/sql/insert , which is the final name.