PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-security.html
Password-Protecting memcached Using SASL SASL support provides the capability to protect your MySQL database from unauthenticated access through memcached clients. Caution Consult this section before deploying the daemon_memcached plugin on a ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/innodb-moving-data-files-offline.html
If moving tablespace files to a different operating system introduces cross-platform replication, it is the database administrator's responsibility to ensure proper replication of DDL statements that contain platform-specific directories. The ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-performance.html
Online 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 responsive ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/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/8.0/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/8.0/en/innodb-redo-log.html
You can try to restart the database with innodb_force_recovery=6 In this case, initialize a new MySQL instance and start the data loading procedure again. The redo log is a disk-based data structure used during crash recovery to correct data ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-temporary-tablespace.html
In this case, a database administrator can remove the global temporary tablespace manually or restart the MySQL server. InnoDB uses session temporary tablespaces and a global temporary tablespace. Session Temporary Tablespaces Session temporary ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-model.html
The InnoDB transaction model aims to 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 ...