PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-prepared-statements-instances-table.html
Prepared statement execution Execution of a COM_STMT_EXECUTE or SQLCOM_PREPARE command for an instrumented prepared statement instance updates the corresponding prepared_statements_instances table row. The Performance Schema provides ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-statement-summary-tables.html
The Performance Schema maintains tables for collecting current and recent statement events, and aggregates that information in summary tables. Section 29.12.6, “Performance Schema Statement Event Tables” describes the events on which statement ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-table-characteristics.html
To change those columns that can be modified, you must have the UPDATE privilege. The name of the performance_schema database is lowercase, as are the names of tables within it. Many tables in the performance_schema database are read only and ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-table-wait-summary-tables.html
For example, columns that aggregate all writes hold the sum of the corresponding columns that aggregate inserts, updates, and deletes. They are the same as the sum of the corresponding xxx_INSERT, xxx_UPDATE, and xxx_DELETE columns. COUNT_UPDATE, ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-thread-filtering.html
The threads table contains a row for each server thread. Each row contains information about a thread and indicates whether monitoring is enabled for it. For the Performance Schema to monitor a thread, these things must be true: The ...
https://dev.mysql.com/doc/refman/8.0/en/query-log.html
However, when using row-based binary logging, updates are sent as row changes rather than SQL statements, and thus these statements are never written to the query log when binlog_format is ROW. A given update also might not be written to the query ... The general query log is a general record of what mysqld is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-administration-pausing.html
This can be useful when you want to pause execution to catch up with events already received from the source, when you want to perform administration on the replica but also ensure that it has processed all updates to a specific point. You can stop ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-blackhole.html
Updates and deletes are handled differently depending on whether statement based or row based logging is in use. When using row-based logging, updates and deletes to such tables are simply skipped—they are not written to the binary log. The ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
A statement invoking a trigger (or function) that causes an update to an AUTO_INCREMENT column is not replicated correctly using statement-based replication. (Bug #45677) A trigger can have triggers for different combinations of trigger event ...
https://dev.mysql.com/doc/refman/8.0/en/replication-functions-async-failover.html
If the replication channel is on a Group Replication primary for a group where failover between replicas is active, the source list is broadcast to all the group members when they join or when it is updated by any method. The replica automatically ... The following functions, which are available from MySQL 8.0.22 for standard source to replica replication and from MySQL 8.0.23 for Group Replication, enable you to add and remove replication source servers from the source list for a replication ...