PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/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.0/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. These are some sample ... 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.0/en/serialized-dictionary-information.html
Other storage engines store SDI data in .sdi files that are created for a given table in the table's database directory. Serialized dictionary information (SDI) is present in all InnoDB tablespace files except for temporary tablespace and undo ...
https://dev.mysql.com/doc/refman/8.0/en/show-grants.html
Note To display nonprivilege information for MySQL accounts, use the SHOW CREATE USER statement. SHOW GRANTS [FOR user_or_role [USING role [, role] ...]] user_or_role: { user (see Section 8.2.4, “Specifying Account Names”) | role (see Section ...
https://dev.mysql.com/doc/refman/8.0/en/charset-applications.html
To create a database such that its tables use a given default character set and collation for data storage, use a CREATE DATABASE statement like this: CREATE DATABASE mydb CHARACTER SET latin1 COLLATE latin1_swedish_ci; Tables created in the ...Note ... For applications that store data using the default MySQL character set and collation (utf8mb4, utf8mb4_0900_ai_ci), no special configuration should be ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-backup-id.html
This table provides a way to find the ID of the backup started most recently for this cluster. The backup_id table contains a single column id, which corresponds to a backup ID taken using the ndb_mgm client START BACKUP command.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-config-values.html
The config_values table provides information about the current state of node configuration parameter values. Each row in the table corresponds to the current value of a parameter on a given node. The config_values table contains the following ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-foreign-keys.html
The foreign_keys table provides information about foreign keys on NDB tables.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-logbuffers.html
The logbuffer table provides information on NDB Cluster log buffer usage. The logbuffers table contains the following columns: node_id The ID of this data node. One each of these log_type rows is shown in the logbuffers table for each data node in ...One of these rows has the log type BACKUP-DATA, which shows the amount of data buffer used during backup to copy fragments to backup ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-threadstat.html
The threadstat table provides a rough snapshot of statistics for threads running in the NDB kernel. Since this table contains counts taken at a given point in time, for best results it is necessary to query this table periodically and store the ...