Search Results
https://dev.mysql.com/doc/refman/8.4/en/partitioning-selection.html
Explicit selection of partitions and subpartitions for rows matching a given WHERE condition is supported. Partition selection is similar to partition pruning, in that only specific partitions are checked for matches, but differs in two key ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-status-monitoring.html
All the historical data generated by the plugin code is still available, but new events for the instruments are not collected. Names for these variables have several forms: Performance_schema_xxx_classes_lost indicates how many instruments of type ...
https://dev.mysql.com/doc/refman/8.4/en/pluggable-authentication-system-variables.html
The file must be generated by the Kerberos server administrator and be copied to a location accessible by the MySQL server. The file name should be given as an absolute path name. If this variable is not set, the default is mysql.keytab in the data ...
https://dev.mysql.com/doc/refman/8.4/en/point-in-time-recovery-binlog.html
The source of information for point-in-time recovery is the set of binary log files generated subsequent to the full backup operation. This section explains the general idea of using the binary log to perform a point-in-time-recovery. The next ...
https://dev.mysql.com/doc/refman/8.4/en/point-in-time-recovery-positions.html
The last section, Section 9.5.1, “Point-in-Time Recovery Using Binary Log”, explains the general idea of using the binary log to perform a point-in-time-recovery. As an example, suppose that around 20:06:00 on March 11, 2020, an SQL statement ...
https://dev.mysql.com/doc/refman/8.4/en/query-log.html
Server restarts and log flushing do not cause a new general query log file to be generated (although flushing closes and reopens it). The general query log is a general record of what mysqld is doing. The server writes information to this log when ...
https://dev.mysql.com/doc/refman/8.4/en/replication-administration-skip.html
If the failing transaction generated an error in a worker thread, you can obtain its GTID directly from the APPLYING_TRANSACTION field in the Performance Schema table replication_applier_status_by_worker. If replication stops due to an issue with ...
https://dev.mysql.com/doc/refman/8.4/en/replication-channels.html
The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error. In MySQL multi-source replication, a replica opens multiple replication channels, one for each source server. The ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-memory.html
This generated event is identifiable by a comment in the binary log, and if GTIDs are in use on the server, it has a GTID assigned. When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
Client transactions are guaranteed to have monotonically increasing GTIDs without gaps between the generated numbers. A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server ...