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-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/5.7/en/innodb-index-types.html
To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize the common lookup and DML operations. Auto-increment column values are unique and are ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locking-reads.html
If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough protection. Can you safely insert the child row to table CHILD? No, because some other session could delete the ...Other transactions can update or delete the same rows you just ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-troubleshoot.html
When defining your own InnoDB table for use with the daemon_memcached plugin, and columns in the table are defined as NOT NULL, ensure that values are supplied for the NOT NULL columns when inserting a record for the table into the ... This section ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-midpoint_insertion.html
Newly read blocks are inserted into the middle of the LRU list. All newly read pages are inserted at a location that by default is 3/8 from the tail of the LRU list. This arrangement divides the LRU list into two segments, where the pages downstream ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-physical-structure.html
When new records are inserted into an InnoDB clustered index, InnoDB tries to leave 1/16 of the page free for future insertions and updates of the index records. If index records are inserted in a sequential order (ascending or descending), the ...
https://dev.mysql.com/doc/refman/5.7/en/memory-storage-engine.html
Deleted rows are put in a linked list and are reused when you insert new data into the table. MEMORY tables also have none of the problems commonly associated with deletes plus inserts in hashed tables. For example, you can put statements such as ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-operations-per-fragment.html
Since NDB does not use single-key access for ordered indexes, the counts for tot_key_reads, tot_key_inserts, tot_key_updates, tot_key_writes, and tot_key_deletes are not incremented by ordered index operations. Note When using tot_key_writes, you ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-import.html
--errins-type=name Command-Line Format --errins-type=name Introduced 5.7.18-ndb-7.6.2 Type Enumeration Default Value [none] Valid Values stopjobstopallsighupsigintlist Error insert type; use list as the name value to obtain all possible values.
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-issues.html
If this occurs, it is entirely possible for new data to be inserted into the source cluster without being recorded in the source SQL node's binary log. In the event of a node failure, errors in replication of NDB tables without primary keys can ...