PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-benefits.html
You can create a new table for data, or use existing tables. The combination of InnoDB tables and memcached offers advantages over using either by themselves. Direct access to the InnoDB storage engine avoids the parsing and planning overhead of SQL. Running memcached in the same process space as the MySQL server avoids the network overhead of passing requests back and ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-security.html
Caution Consult this section before deploying the daemon_memcached plugin on a production server, or even on a test server if the MySQL instance contains sensitive data. Because memcached does not use an authentication mechanism by default, and the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-troubleshoot.html
These limits primarily apply if you intend to create an index on a value column to run report-generating queries on that column using SQL. This section describes issues that you may encounter when using the InnoDB memcached plugin. If you encounter ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-txn.html
This option is less appropriate when accessing the same tables through both memcached and SQL, because it blocks CREATE INDEX statements on the tables, which could be important for running reporting queries. Unlike traditional memcached, the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-performance.html
Session 1: mysql> CREATE TABLE t1 (c1 INT) ENGINE=InnoDB; mysql> START TRANSACTION; mysql> SELECT * FROM t1; The session 1 SELECT statement takes a shared metadata lock on table t1. Online DDL improves several aspects of MySQL operation: ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-optimizer-statistics.html
You can use the STATS_PERSISTENT, STATS_AUTO_RECALC, and STATS_SAMPLE_PAGES clauses with CREATE TABLE and ALTER TABLE statements to configure optimizer statistics for individual tables. This section describes how to configure persistent and ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-physical-structure.html
InnoDB performs a bulk load when creating or rebuilding B-tree indexes. This method of index creation is known as a sorted index build. With the exception of spatial indexes, InnoDB indexes are B-tree data structures. Spatial indexes use R-trees, ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-purge-configuration.html
The reason that a long running transaction can cause the History list length to increase is that under a consistent read transaction isolation level such as REPEATABLE READ, a transaction must return the same result as when the read view for that ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-recovery.html
In some cases of database corruption, it is enough to dump, drop, and re-create one or a few corrupt tables. To achieve point-in-time recovery after restoring a backup, you can apply changes from the binary log that occurred after the backup was ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-statistics-estimation.html
Optimizer statistics are not persisted to disk when innodb_stats_persistent=OFF or when individual tables are created or altered with STATS_PERSISTENT=0. Instead, statistics are stored in memory, and are lost when the server is shut down. Statistics ...