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-file-format-compatibility-checking.html
The file format tag is a “high water mark”, and as such it is increased after the server is started, if a table in a “higher” format is created or an existing table is accessed for read or write (assuming its format is supported). If you ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-examples-compression-sect.html
The smallest PAGE_SIZE in INNODB_CMPMEM is used for block descriptors of those compressed pages for which no uncompressed page exists in the buffer pool. Indirectly, we see that 259 (6169-5910) compressed pages also exist in the buffer pool in ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locking-reads.html
Consistent reads ignore any locks set on the records that exist in the read view. First, use a consistent read to query the table PARENT and verify that the parent row exists. If you query data and then insert or update related data within the same ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-developing.html
Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or adapting existing code that uses MySQL or the memcached API. You might reuse some existing code that works with the memcached API, but adaptation ...With the daemon_memcached plugin, instead of many traditional memcached servers running on low-powered machines, you have the same number of memcached servers as MySQL servers, running on relatively high-powered machines with substantial disk storage and ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-internals.html
If multiple InnoDB table columns are mapped, there is a check to ensure that each column exists and is the right type. InnoDB API for the InnoDB memcached Plugin The InnoDB memcached engine accesses InnoDB through InnoDB APIs, most of which are ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-memcached.html
Thus, new entries are visible as soon as you use the associated table identifier, but changes to existing entries require a server restart before they take effect. This is because InnoDB performs best for large-scale insertions if primary key values ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-page-compression.html
Writes to the tablespace that occur after setting the new compression algorithm use the new setting, but to apply the new compression algorithm to existing pages, you must rebuild the table using OPTIMIZE TABLE. To uncompress existing pages, you ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-undo-tablespaces.html
Existing transactions that are currently using rollback segments are permitted to finish. Undo tablespaces contain undo logs, which are collections of records containing information about how to undo the latest change by a transaction to a ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-file-plugin.html
As of MySQL 5.7.17, to ensure that keys are flushed only when the correct keyring storage file exists, keyring_file stores a SHA-256 checksum of the keyring in the file. The keyring_file keyring plugin stores keyring data in a file local to the ...
https://dev.mysql.com/doc/refman/5.7/en/macos-installation-notes.html
You can do this through the Directory Utility, and the mysql user should already exist. For use in single user mode, an entry for _mysql (note the underscore prefix) should already exist within the system /etc/passwd file. You should keep the ...