Search Results
https://dev.mysql.com/doc/refman/8.4/en/myisamchk-other-options.html
myisamchk supports the following options for actions other than table checks and repairs: --analyze, -a Command-Line Format --analyze Analyze the distribution of key values. This improves join performance by enabling the join optimizer to better ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-disk-data-storage-requirements.html
The following items apply to Disk Data storage requirements: Variable-length columns of Disk Data tables take up a fixed amount of space. You can obtain an estimate the amount of space available in data files and undo log files by querying the ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-programs-ndb-size-pl.html
Options that can be used with ndb_size.pl are shown in the following table. Similarly, you can cause specific tables to be skipped by listing their names, separated by commas, following the optional --excludetables option. Memory requirements for ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-atom-molecule-events.html
For a table I/O event, there are usually two rows in events_waits_current, not one. For example, a row fetch might result in rows like this: Row# EVENT_NAME TIMER_START TIMER_END ---- ---------- ----------- --------- 1 wait/io/file/myisam/dfile ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-query-profiling.html
The setup_actors table can be used to limit the collection of historical events by host, user, or account to reduce runtime overhead and the amount of data collected in history tables. For example: mysql> SELECT * FROM employees.employees WHERE ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-runtime-configuration.html
If you have the UPDATE privilege, you can change Performance Schema operation by modifying setup tables to affect how monitoring occurs. For additional details about these tables, see Section 29.12.2, “Performance Schema Setup Tables”. The ...
https://dev.mysql.com/doc/refman/8.4/en/point-in-time-recovery-positions.html
As an example, suppose that around 20:06:00 on March 11, 2020, an SQL statement was executed that deleted a table. You can perform a point-in-time recovery to restore the server up to its state right before the table deletion. In our example, given ... 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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-triggers.html
If an upgraded replication source server still has old replicas using MySQL versions that do not support multiple triggers, an error occurs on those replicas if a trigger is created on the source for a table that already has a trigger with the same ... With statement-based replication, triggers executed on the source also execute on the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-monitoring.html
To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. The information that was available through these variables has been migrated to the replication performance tables. This ...
https://dev.mysql.com/doc/refman/8.4/en/sys-schema-progress-reporting.html
The following sys schema views provide progress reporting for long-running transactions: processlist session x$processlist x$session Assuming that the required instruments and consumers are enabled, the progress column of these views shows the ...