PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-tuning.html
get key_value Using System Memory For best performance, deploy the daemon_memcached plugin on machines that are configured as typical database servers, where the majority of system RAM is devoted to the InnoDB buffer pool, through the ... Because ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-performance.html
In-place operations avoid the disk I/O and CPU cycles associated with the table-copy method, which minimizes overall load on the database. Online DDL improves several aspects of MySQL operation: Applications that access the table are more ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-optimizer-statistics.html
You can manually modify the mysql.innodb_table_stats and mysql.innodb_index_stats tables to force a specific query optimization plan or to test alternative plans without modifying the database. This section describes how to configure persistent and ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-ro-txn.html
In this case, attempting to make changes to the database (for InnoDB, MyISAM, or other types of tables) causes an error, and the transaction continues in read-only state: ERROR 1792 (25006): Cannot execute statement in a READ ONLY transaction.
https://dev.mysql.com/doc/refman/5.7/en/innodb-purge-configuration.html
InnoDB does not physically remove a row from the database immediately when you delete it with an SQL statement. A row and its index records are only physically removed when InnoDB discards the undo log record written for the deletion. This removal ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-temporary-tablespace.html
In this case, a database administrator can remove the temporary tablespace manually or restart the server, which removes and recreates the temporary tablespace automatically. Non-compressed, user-created temporary tables and on-disk internal ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-model.html
The InnoDB transaction model aims combine the best properties of a multi-versioning database with traditional two-phase locking. InnoDB performs locking at the row level and runs queries as nonlocking consistent reads by default, in the style of ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-turning-off.html
Oracle recommends InnoDB as the preferred storage engine for typical database applications, from single-user wikis and blogs running on a local system, to high-end applications pushing the limits of performance. In MySQL 5.7, InnoDB is the default ...
https://dev.mysql.com/doc/refman/5.7/en/internal-locking.html
This means that the database or table supports different views for the data depending on when access begins. This section discusses internal locking; that is, locking performed within the MySQL server itself to manage contention for table contents ...
https://dev.mysql.com/doc/refman/5.7/en/json-utility-functions.html
JSON_PRETTY(json_val) Provides pretty-printing of JSON values similar to that implemented in PHP and by other languages and database systems. This section documents utility functions that act on JSON values, or strings that can be parsed as JSON ...