Search Results
https://dev.mysql.com/doc/refman/8.4/en/fulltext-search.html
For large data sets, it is much faster to load your data into a table that has no FULLTEXT index and then create the index after that, than to load data into a table that has an existing FULLTEXT index. MATCH (col1,col2,...) AGAINST (expr ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-enterprise-backup.html
Supply the old server UUID by copying the auto.cnf file preserved in step 2 above into the data directory of the restored member. Copy the mysqld-auto.cnf file from another member of the group into the restored server's data directory, if that ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-member-actions.html
When the feature is active and correctly configured, if the primary that is replicating goes offline or into an error state, the new primary starts replication on the same channel when it is elected. If the primary goes offline or into an error ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-multi-primary-mode.html
You can choose a setting that suits the workload of your group and your priorities for data reads and writes, taking into account the performance impact of the synchronization required to increase consistency. (In a group that is running in ... In ...
https://dev.mysql.com/doc/refman/8.4/en/ibd2sdi.html
See http://dev.mysql.com/doc/refman/8.4/en/dbug-package.html -d, --dump-file=name Dump the tablespace SDI into the file passed by user. --dump-file=, -d Command-Line Format --dump-file=file Type File name Default Value [none] Dumps serialized ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-backup.html
Copy all InnoDB data files (ibdata files and .ibd files) into a safe place. Dumped tables are stored into text files that are human-readable, so spotting table corruption becomes easier. The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, which can be used directly by the mysqld server for faster ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-syntax-warnings.html
The “non-strict” behavior lets you import a mysqldump file into a database that does not support compressed tables, even if the source database contained compressed tables. To import the dump file into a new database, and have the tables ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-data-encryption.html
Once redo log data is read into memory, it is in unencrypted form. Once undo log data is read into memory, it is in unencrypted form. InnoDB supports data-at-rest encryption for file-per-table tablespaces, general tablespaces, the mysql system ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-io.html
Read-Ahead If InnoDB can determine there is a high probability that data might be needed soon, it performs read-ahead operations to bring that data into the buffer pool so that it is available in memory. In random read-ahead, if InnoDB notices that ... InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-performance.html
Online operations read less data into the buffer pool than table-copy operations, which reduces purging of frequently accessed data from memory. Online DDL and Metadata Locks Online DDL operations can be viewed as having three phases: Phase 1: ...