Skip to content

Commit

Permalink
performance_schema -> information_schema (#6418) (#6430)
Browse files Browse the repository at this point in the history
ti-chi-bot authored Sep 9, 2021

Verified

This commit was signed with the committer’s verified signature.
gregorjerse Gregor Jerše
1 parent 35f6ffb commit 8cb0eac
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions statement-summary-tables.md
Original file line number Diff line number Diff line change
@@ -8,7 +8,7 @@ aliases: ['/docs/stable/statement-summary-tables/','/docs/v4.0/statement-summary

To better handle SQL performance issues, MySQL has provided [statement summary tables](https://dev.mysql.com/doc/refman/5.6/en/statement-summary-tables.html) in `performance_schema` to monitor SQL with statistics. Among these tables, `events_statements_summary_by_digest` is very useful in locating SQL problems with its abundant fields such as latency, execution times, rows scanned, and full table scans.

Therefore, starting from v4.0.0-rc.1, TiDB provides system tables in `information_schema`. These system tables are similar to `events_statements_summary_by_digest` in terms of features.
Therefore, starting from v4.0.0-rc.1, TiDB provides system tables in `information_schema` (_not_ `performance_schema`) that are similar to `events_statements_summary_by_digest` in terms of features.

- [`statements_summary`](#statements_summary)
- [`statements_summary_history`](#statements_summary_history)
@@ -19,7 +19,7 @@ This document details these tables and introduces how to use them to troubleshoo

## `statements_summary`

`statements_summary` is a system table in `performance_schema`. `statements_summary` groups the SQL statements by the SQL digest and the plan digest, and provides statistics for each SQL category.
`statements_summary` is a system table in `information_schema`. `statements_summary` groups the SQL statements by the SQL digest and the plan digest, and provides statistics for each SQL category.

The "SQL digest" here means the same as used in slow logs, which is a unique identifier calculated through normalized SQL statements. The normalization process ignores constant, blank characters, and is case insensitive. Therefore, statements with consistent syntaxes have the same digest. For example:

0 comments on commit 8cb0eac

Please sign in to comment.