Search Results
https://dev.mysql.com/doc/mysql-em-plugin/en/myoem-config-metric-innodbfulltext-category.html
Table 7.15 InnoDB Fulltext Configuration Metrics NameDescriptionAux Table Specifies the qualified name of an InnoDB table containing a FULLTEXT index. Cache Size Size of the cache that holds a parsed document in memory while creating an InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
A table and all of its indexes use the same (compressed) page size. It might be that the primary key (clustered) index, which contains the data for all columns of a table, compresses more effectively than the secondary indexes. Another way to test ... Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-introduction.html
Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Each InnoDB table has a primary key index called the clustered index that organizes the data to ...
https://dev.mysql.com/doc/refman/8.4/en/merge-table-advantages.html
A MERGE table need not maintain an index of its own because it uses the indexes of the individual tables. (You must still specify the index definitions when you create a MERGE table, even though no indexes are created.) If you have a set of tables ... MERGE tables can help you solve the following problems: Easily manage a set of log ...
https://dev.mysql.com/doc/mysql-em-plugin/en/myoem-query-analyzer-ref.html
The Query Analyzer provides a point-in-time snapshot of queries on the monitored database, enabling you to monitor SQL statements executed on a MySQL server and see details of each query, number of executions, and execution times. Important This ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-logging.html
The mysql client can do these types of logging for statements executed interactively: On Unix, mysql writes the statements to a history file. On all platforms, if the --syslog option is given, mysql writes the statements to the system logging ...By ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-gtids.html
A SET @@GLOBAL.gtid_purged statement was issued on MySQL 5.7.7 or earlier, and the binary log that was active at the time of the SET @@GLOBAL.gtid_purged statement has not yet been purged. enforce_gtid_consistency Command-Line Format ... The MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks.html
You can create a user account with the appropriate privileges to apply the transactions that are normally replicated on a channel, and specify this as the PRIVILEGE_CHECKS_USER account for the replication applier, using a CHANGE REPLICATION SOURCE ... By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by another server are applied on a replica or group ...
https://dev.mysql.com/doc/refman/8.4/en/set-variable.html
A SET statement that assigns variable values is not written to the binary log, so in replication scenarios it affects only the host on which you execute it. To affect all replication hosts, execute the statement on each host. Many system variables ...variable: { user_var_name | param_name | local_var_name | {GLOBAL | @@GLOBAL.} system_var_name | {PERSIST | @@PERSIST.} system_var_name | {PERSIST_ONLY | @@PERSIST_ONLY.} system_var_name | [SESSION | ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-unsupported.html
If a prefix is used as part of an index specification in a statement such as CREATE TABLE, ALTER TABLE, or CREATE INDEX, the prefix is not created by NDB. A statement containing an index prefix, and creating or modifying an NDB table, must still be ...Statements referencing such features, even if effectively ignored by NDB, must be syntactically and otherwise ...