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-replication.html
It is assumed that you have completed the setup described in Section 14.21.3, “Setting Up the InnoDB memcached Plugin”. Enabling the InnoDB memcached Binary Log To use the daemon_memcached plugin with the MySQL binary log, enable the ... Because ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Therefore, page compression only works if page data can be compressed to a size that is less than or equal to the InnoDB page size minus the file system ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-ro-txn.html
InnoDB can avoid the overhead associated with setting up the transaction ID (TRX_ID field) for transactions that are known to be read-only. InnoDB detects read-only transactions when: The transaction is started with the START TRANSACTION READ ONLY ...A transaction ID is only needed for a transaction that might perform write operations or locking reads such as SELECT ...
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/innodb-and-mysql-replication.html
For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica. Cascading actions for InnoDB tables on the source are executed on the replica only if the tables sharing the foreign key relation use ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-backup-recovery.html
This section covers topics related to InnoDB backup and recovery. For information about backup techniques applicable to InnoDB, see Section 14.19.1, “InnoDB Backup”. For information about point-in-time recovery, recovery from disk failure or ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks.html
For a deadlock example, see Section 14.7.5.1, “An InnoDB Deadlock Example”. When deadlock detection is enabled (the default) and a deadlock does occur, InnoDB detects the condition and rolls back one of the transactions (the victim). If deadlock ... A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-memcached.html
This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are with auto-increment values). If you store several different classes of information using memcached, consider setting up a ...
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/optimizing-innodb-queries.html
To tune queries for InnoDB tables, create an appropriate set of indexes on each table. Follow these guidelines for InnoDB indexes: Because each InnoDB table has a primary key (whether you request one or not), specify a set of primary key columns ...