PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
21.7.9.1 NDB Cluster Replication: Automating Synchronization of the Replica to the Source Binary Log
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-auto-sync.html
It is possible to automate much of the process described in the previous section (see Section 21.7.9, “NDB Cluster Backups With NDB Cluster Replication”). The following Perl script reset-replica.pl serves as an example of how you can do this.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-connection-tables.html
The Performance Schema also counts internal threads and threads for user sessions that failed to authenticate, using rows with USER and HOST column values of NULL. When a client connects to the MySQL server, it does so under a particular user name ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-consumer-filtering.html
Conversely, you can get detailed statements in events_statements_current without digests (the DIGEST and DIGEST_TEXT columns are NULL). To enable or disable a consumer, set its ENABLED value to YES or NO. If you disable a consumer, the server does ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-hosts-table.html
This is NULL for an internal thread, or for a user session that failed to authenticate. The hosts table contains a row for each host from which clients have connected to the MySQL server. For each host name, the table counts the current and total ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-queries.html
Pre-filtering limits which event information is collected and is independent of any particular user. By contrast, post-filtering is performed by individual users through the use of queries with appropriate WHERE clauses that restrict what event ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-replication-applier-status-table.html
This table shows the current general transaction execution status on the replica. The table provides information about general aspects of transaction applier status that are not specific to any thread involved. Thread-specific status information is ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-restrictions.html
If the values in this table for a given timer name are NULL, that timer is not supported on your platform. The Performance Schema avoids using mutexes to collect or produce data, so there are no guarantees of consistency and results can sometimes ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-rwlock-instances-table.html
WRITE_LOCKED_BY_THREAD_ID When a thread currently has an rwlock locked in exclusive (write) mode, WRITE_LOCKED_BY_THREAD_ID is the THREAD_ID of the locking thread, otherwise it is NULL. The rwlock_instances table lists all the rwlock (read write ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-setup-instruments-table.html
Events produced by the instrument have NULL for the TIMER_START, TIMER_END, and TIMER_WAIT timer values. The setup_instruments table lists classes of instrumented objects for which events can be collected: mysql> SELECT * FROM ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-summary-tables.html
Generally, the effect is to reset the summary columns to 0 or NULL, not to remove rows. Summary tables provide aggregated information for terminated events over time. The tables in this group summarize event data in different ways. Each summary ...