Search Results
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-bulk-data-loading.html
For optimal performance when loading data into an InnoDB FULLTEXT index, follow this set of steps: Define a column FTS_DOC_ID at table creation time, of type BIGINT UNSIGNED NOT NULL, with a unique index named FTS_DOC_ID_INDEX. For example: CREATE ... These performance tips supplement the general guidelines for fast inserts in Section 10.2.5.1, “Optimizing INSERT ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-storage-layout.html
For tables that are big, or contain lots of repetitive text or numeric data, consider using COMPRESSED row format. Once your data reaches a stable size, or a growing table has increased by tens or some hundreds of megabytes, consider using the ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-queries-myisam.html
For MyISAM tables that change frequently, try to avoid all variable-length columns (VARCHAR, BLOB, and TEXT). Some general tips for speeding up queries on MyISAM tables: To help MySQL better optimize queries, use ANALYZE TABLE or run myisamchk ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-columns.html
The next two sections discuss COLUMNS partitioning, which are variants on RANGE and LIST partitioning. COLUMNS partitioning enables the use of multiple columns in partitioning keys. All of these columns are taken into account both for the purpose ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-key.html
Partitioning by key is similar to partitioning by hash, except that where hash partitioning employs a user-defined expression, the hashing function for key partitioning is supplied by the MySQL server. NDB Cluster uses MD5() for this purpose; for ...
https://dev.mysql.com/doc/refman/8.4/en/partitioning-maintenance.html
If you have deleted a large number of rows from a partition or if you have made many changes to a partitioned table with variable-length rows (that is, having VARCHAR, BLOB, or TEXT columns), you can use ALTER TABLE ... A number of table and ...
https://dev.mysql.com/doc/refman/8.4/en/password-security-user.html
Passwords can be written as plain text in SQL statements such as CREATE USER and ALTER USER, so if you use these statements, they are logged in the history file. MySQL users should use the following guidelines to keep passwords secure. When you run ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-replication-tables.html
The Executed_Gtid_Set field can show a large set with a great deal of text. This is similar to the information available from the SHOW REPLICA STATUS statement, but representation in table form is more accessible and has usability benefits: SHOW ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-statement-summary-tables.html
(The DIGEST_TEXT column contains the corresponding normalized statement digest text, but is neither a grouping nor a summary column. The QUERY_SAMPLE_TEXT, QUERY_SAMPLE_SEEN, and QUERY_SAMPLE_TIMER_WAIT columns also are neither grouping nor summary ... The Performance Schema maintains tables for collecting current and recent statement events, and aggregates that information in summary ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-system-variables.html
performance_schema_max_sql_text_length Command-Line Format --performance-schema-max-sql-text-length=# System Variable performance_schema_max_sql_text_length Scope Global Dynamic No SET_VAR Hint Applies No Type Integer Default Value 1024 Minimum ...