Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 38.5Mb
PDF (A4) - 38.5Mb
PDF (RPM) - 33.3Mb
HTML Download (TGZ) - 8.1Mb
HTML Download (Zip) - 8.2Mb
HTML Download (RPM) - 7.0Mb
Man Pages (TGZ) - 134.2Kb
Man Pages (Zip) - 190.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

MySQL 8.0 Reference Manual  /  ...  /  The user_summary_by_statement_type and x$user_summary_by_statement_type Views

26.4.3.46 The user_summary_by_statement_type and x$user_summary_by_statement_type Views

These views summarize informaion about statements executed, grouped by user and statement type. By default, rows are sorted by user and descending total latency.

The user_summary_by_statement_type and x$user_summary_by_statement_type views have these columns:

  • user

    The client user name. Rows for which the USER column in the underlying Performance Schema table is NULL are assumed to be for background threads and are reported with a host name of background.

  • statement

    The final component of the statement event name.

  • total

    The total number of occurrences of the statement event for the user.

  • total_latency

    The total wait time of timed occurrences of the statement event for the user.

  • max_latency

    The maximum single wait time of timed occurrences of the statement event for the user.

  • lock_latency

    The total time waiting for locks by timed occurrences of the statement event for the user.

  • rows_sent

    The total number of rows returned by occurrences of the statement event for the user.

  • rows_examined

    The total number of rows read from storage engines by occurrences of the statement event for the user.

  • rows_affected

    The total number of rows affected by occurrences of the statement event for the user.

  • full_scans

    The total number of full table scans by occurrences of the statement event for the user.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.