Rechercher dans le manuel MySQL
26.12.17.11 Error Summary Tables
The Performance Schema maintains summary tables for aggregating statistical information about server errors (and warnings). For a list of server errors, see Section B.3.1, “Server Error Message Reference”.
Collection of error information is controlled by the
error
instrument, which is enabled by
default. Timing information is not collected.
Each error summary table has three columns that identify the error:
ERROR_NUMBER
is the numeric error value. The value is unique.ERROR_NAME
is the symbolic error name corresponding to theERROR_NUMBER
value. The value is unique.SQLSTATE
is the SQLSTATE value corresponding to theERROR_NUMBER
value. The value is not necessarily unique.
For example, if ERROR_NUMBER
is 1050,
ERROR_NAME
is
ER_TABLE_EXISTS_ERROR
and
SQLSTATE
is 42S01
.
Example error event summary information:
- FROM performance_schema.events_errors_summary_global_by_error
- *************************** 1. row ***************************
- ERROR_NUMBER: 1064
- ERROR_NAME: ER_PARSE_ERROR
- SQL_STATE: 42000
- SUM_ERROR_RAISED: 1
- SUM_ERROR_HANDLED: 0
- FIRST_SEEN: 2016-06-28 07:34:02
- LAST_SEEN: 2016-06-28 07:34:02
- *************************** 2. row ***************************
- ERROR_NUMBER: 1146
- ERROR_NAME: ER_NO_SUCH_TABLE
- SQL_STATE: 42S02
- SUM_ERROR_RAISED: 2
- SUM_ERROR_HANDLED: 0
- FIRST_SEEN: 2016-06-28 07:34:05
- LAST_SEEN: 2016-06-28 07:36:18
- *************************** 3. row ***************************
- ERROR_NUMBER: 1317
- ERROR_NAME: ER_QUERY_INTERRUPTED
- SQL_STATE: 70100
- SUM_ERROR_RAISED: 1
- SUM_ERROR_HANDLED: 0
- FIRST_SEEN: 2016-06-28 11:01:49
- LAST_SEEN: 2016-06-28 11:01:49
Each error summary table has one or more grouping columns to indicate how the table aggregates errors:
events_errors_summary_by_account_by_error
hasUSER
,HOST
, andERROR_NUMBER
columns. Each row summarizes events for a given account (user and host combination) and error.events_errors_summary_by_host_by_error
hasHOST
andERROR_NUMBER
columns. Each row summarizes events for a given host and error.events_errors_summary_by_thread_by_error
hasTHREAD_ID
andERROR_NUMBER
columns. Each row summarizes events for a given thread and error.events_errors_summary_by_user_by_error
hasUSER
andERROR_NUMBER
columns. Each row summarizes events for a given user and error.events_errors_summary_global_by_error
has anERROR_NUMBER
column. Each row summarizes events for a given error.
Each error summary table has these summary columns containing aggregated values:
SUM_ERROR_RAISED
This column aggregates the number of times the error occurred.
SUM_ERROR_HANDLED
This column aggregates the number of times the error was handled by an SQL exception handler.
FIRST_SEEN
,LAST_SEEN
Timestamp indicating when the error was first seen and most recently seen.
A NULL
row in each error summary table is
used to aggregate statistics for all errors that lie out of
range of the instrumented errors. For example, if MySQL Server
errors lie in the range from M
to
N
and an error is raised with
number Q
not in that range, the
error is aggregated in the NULL
row. The
NULL
row is the row with
ERROR_NUMBER=0
,
ERROR_NAME=NULL
, and
SQLSTATE=NULL
.
The error summary tables have these indexes:
events_errors_summary_by_account_by_error
:Primary key on (
USER
,HOST
,ERROR_NUMBER
)
events_errors_summary_by_host_by_error
:Primary key on (
HOST
,ERROR_NUMBER
)
events_errors_summary_by_thread_by_error
:Primary key on (
THREAD_ID
,ERROR_NUMBER
)
events_errors_summary_by_user_by_error
:Primary key on (
USER
,ERROR_NUMBER
)
events_errors_summary_global_by_error
:Primary key on (
ERROR_NUMBER
)
TRUNCATE TABLE
is permitted for
error summary tables. It has these effects:
For summary tables not aggregated by account, host, or user, truncation resets the summary columns to zero or
NULL
rather than removing rows.For summary tables aggregated by account, host, or user, truncation removes rows for accounts, hosts, or users with no connections, and resets the summary columns to zero or
NULL
for the remaining rows.
In addition, each error summary table that is aggregated by
account, host, user, or thread is implicitly truncated by
truncation of the connection table on which it depends, or
truncation of
events_errors_summary_global_by_error
.
For details, see
Section 26.12.8, “Performance Schema Connection Tables”.
Nederlandse vertaling
U hebt gevraagd om deze site in het Nederlands te bezoeken. Voor nu wordt alleen de interface vertaald, maar nog niet alle inhoud.Als je me wilt helpen met vertalingen, is je bijdrage welkom. Het enige dat u hoeft te doen, is u op de site registreren en mij een bericht sturen waarin u wordt gevraagd om u toe te voegen aan de groep vertalers, zodat u de gewenste pagina's kunt vertalen. Een link onderaan elke vertaalde pagina geeft aan dat u de vertaler bent en heeft een link naar uw profiel.
Bij voorbaat dank.
Document heeft de 26/06/2006 gemaakt, de laatste keer de 26/10/2018 gewijzigd
Bron van het afgedrukte document:https://www.gaudry.be/nl/mysql-rf-error-summary-tables.html
De infobrol is een persoonlijke site waarvan de inhoud uitsluitend mijn verantwoordelijkheid is. De tekst is beschikbaar onder CreativeCommons-licentie (BY-NC-SA). Meer info op de gebruiksvoorwaarden en de auteur.
Referenties
Deze verwijzingen en links verwijzen naar documenten die geraadpleegd zijn tijdens het schrijven van deze pagina, of die aanvullende informatie kunnen geven, maar de auteurs van deze bronnen kunnen niet verantwoordelijk worden gehouden voor de inhoud van deze pagina.
De auteur Deze site is als enige verantwoordelijk voor de manier waarop de verschillende concepten, en de vrijheden die met de referentiewerken worden genomen, hier worden gepresenteerd. Vergeet niet dat u meerdere broninformatie moet doorgeven om het risico op fouten te verkleinen.