Search Results
MySQL 8.4 Reference Manual :: A.11 MySQL 8.4 FAQ: MySQL Chinese, Japanese, and Korean Character Sets
https://dev.mysql.com/doc/refman/8.4/en/faqs-cjk.html
This set of Frequently Asked Questions derives from the experience of MySQL's Support and Development groups in handling many inquiries about CJK (Chinese-Japanese-Korean) issues. What problems should I be aware of when working with the Big5 ...
https://dev.mysql.com/doc/refman/8.4/en/generated-column-index-optimizations.html
For example: CREATE TABLE t1 (f1 INT, gc INT AS (f1 + 1) STORED, INDEX (gc)); The generated column, gc, is defined as the expression f1 + 1. The column is also indexed and the optimizer can take that index into account during execution plan ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-buffer-page-lru-table.html
The INNODB_BUFFER_PAGE_LRU table provides information about the pages in the InnoDB buffer pool; in particular, how they are ordered in the LRU list that determines which pages to evict from the buffer pool when it becomes full. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-change-buffer.html
During this time, disk I/O is increased, which can cause a significant slowdown for disk-bound queries. To avoid impacting performance, reproduce the issue you want to investigate on a test instance and run your queries on the test instance. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
Whether the workload is more like a data warehouse (primarily queries) or an OLTP system (mix of queries and DML). For more elaborate tests involving workloads with multiple compressed tables, run queries against the Information Schema ... Most ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-read-only-instance.html
You might use this technique to avoid bottlenecks that can occur with a heavily loaded MySQL instance, or you might use different configuration options for the various instances to tune each one for particular kinds of queries. See Section 10.5.3, ... You can query InnoDB tables where the MySQL data directory is on read-only media by enabling the --innodb-read-only configuration option at server ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-redo-log.html
The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete transactions. During normal operations, the redo log encodes requests to change table data that result from SQL statements or low-level API ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-standard-monitor.html
Contention can be due to heavy parallelism of queries or problems in operating system thread scheduling. You can calculate from these numbers how many data file I/O operations your queries currently are doing. The Lock Monitor is the same as the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-undo-tablespaces.html
Undo tablespaces contain undo logs, which are collections of records containing information about how to undo the latest change by a transaction to a clustered index record. Default undo tablespaces are created at initialization time to provide a ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-install-example-data.html
Running SELECT queries on the SQL node is no different from running them on any other instance of a MySQL server. To run queries from the command line, you first need to log in to the MySQL Monitor in the usual way (specify the root password at the ... Note The information in this section applies to NDB Cluster running on both Unix and Windows ...