Search Results
https://dev.mysql.com/doc/extending-mysql/8.4/en/mysql-threads.html
This thread also normally handles alarms and calls process_alarm() to force timeouts on connections that have been idle too long. The MySQL server creates the following threads: Connection manager threads handle client connection requests on the ...
https://dev.mysql.com/doc/relnotes/mysql-router/8.4/en/news-8-2-0.html
(WL #12794) Bugs Fixed Queries larger than 16MB were not properly handled if Connection Sharing was enabled. (Bug #35574557) If an invalid client greeting was received, the following message was logged: loop(): Input too short This message was not ... Deprecation and Removal Notes Functionality Added or Changed Bugs Fixed Deprecation and Removal Notes The allow_primary_reads parameter of the destinations URI is now deprecated and subject to removal in a future version of MySQL ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/innodb-clusterset-status.html
Some members might be offline, or the cluster might have too few members to provide tolerance for failures. This section describes the following: InnoDB ClusterSet Status InnoDB ClusterSet Topology MySQL Router Status for InnoDB ClusterSet InnoDB ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/set-replicaset-primary.html
If this synchronization step takes too long or is not possible on any of the secondary instances, the operation is aborted. Use the ReplicaSet.setPrimaryInstance() operation to safely perform a change of the primary of a ReplicaSet to another ...
https://dev.mysql.com/doc/mysql-ai/9.4/en/mys-ai-aml-scoring-a-forecasting-model.html
You should also use a larger number of records for training and validation to get a valid score. mysql> CALL sys.ML_MODEL_UNLOAD('forecasting_use_case'); To avoid consuming too much memory, it is good practice to unload a model when you are finished ... After generating predictions, you can score the model to assess its ...
https://dev.mysql.com/doc/mysql-ai/9.4/en/mys-ai-aml-scoring-a-recommendation-model.html
You should also use a larger number of records for training and validation to get a valid score. mysql> CALL sys.ML_MODEL_UNLOAD('recommendation_use_case'); To avoid consuming too much memory, it is good practice to unload a model when you are ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-queries-myisam.html
It is normally not useful to split a table into different tables just because the rows become large. The only cases where splitting up a table makes an appreciable difference is if it is a MyISAM table using dynamic row format that you can change to ...This updates a value for each index part that indicates the average number of rows that have the same ... Some general tips for speeding up queries on MyISAM tables: To help MySQL better ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-operations-per-fragment.html
Note When using tot_key_writes, you should keep in mind that a write operation in this context updates the row if the key exists, and inserts a new row otherwise. Generally, such a refusal is due to duplicate keys (inserts), Key not found errors ...
https://dev.mysql.com/doc/mysql-enterprise-backup/8.4/en/glossary.html
These techniques have different characteristics in terms of size and representation of the backup data, and speed (especially speed of the restore operation). compression A technique that produces smaller backup files, with size reduction influenced ... These terms are commonly used in information about the MySQL Enterprise Backup ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-syntax-warnings.html
SQL Compression Syntax Warnings and Errors for File-Per-Table Tablespaces When innodb_strict_mode is enabled (the default), specifying ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE in CREATE TABLE or ALTER TABLE statements produces the following error if ...mysql> SHOW WARNINGS; +---------+------+---------------------------------------------------------------+ | Level | Code | Message | +---------+------+---------------------------------------------------------------+ | Warning | 1478 | InnoDB: KEY_BLOCK_SIZE requires ...