PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 296.3Kb
Man Pages (Zip)
- 401.7Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-tuning.html
For existence checking, you typically only store a very # short value such as "1". Reducing Transactional Overhead A default value of 1 for daemon_memcached_r_batch_size and daemon_memcached_w_batch_size is intended for maximum reliability of ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-txn.html
By default, data written through the memcached interface is stored to disk, and calls to get return the most recent value from disk. Storing Data on Disk, in Memory, or Both The innodb_memcache.cache_policies table specifies whether to store data ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached.html
The InnoDB memcached plugin (daemon_memcached) provides an integrated memcached daemon that automatically stores and retrieves data from InnoDB tables, turning the MySQL server into a fast “key-value store”. Data modified through memcached ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-schema.html
You should be familiar with performance_schema tables that store InnoDB event data. Tables relevant to InnoDB-related events include: The Wait Event tables, which store wait events. Stage Event tables, which store event data for InnoDB ALTER TABLE ... This section provides a brief introduction to InnoDB integration with Performance ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-component-installation.html
MySQL provides these keyring component choices: component_keyring_file: Stores keyring data in a file local to the server host. component_keyring_encrypted_file: Stores keyring data in an encrypted, password-protected file local to the server host.
https://dev.mysql.com/doc/refman/8.0/en/keyring-component-plugin-comparison.html
The MySQL Keyring originally implemented keystore capabilities using server plugins, but began transitioning to use the component infrastructure in MySQL 8.0.24. In the operating system file where persisted system variables are stored, the names ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-encrypted-file-component.html
The component_keyring_encrypted_file keyring component stores keyring data in an encrypted, password-protected file local to the server host. To use component_keyring_encrypted_file for keystore management, you must: Write a manifest that tells the ... Note component_keyring_encrypted_file is an extension included in MySQL Enterprise Edition, a commercial ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-file-plugin.html
The keyring_file keyring plugin stores keyring data in a file local to the server host. 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. As of ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-functions-plugin-specific.html
keyring_aws_rotate_keys() Associated keyring plugin: keyring_aws keyring_aws_rotate_keys() rotates keys stored in the keyring_aws storage file named by the keyring_aws_data_file system variable. Rotation sends each key stored in the file to AWS KMS ... For each keyring plugin-specific function, this section describes its purpose, calling sequence, and return ...
https://dev.mysql.com/doc/refman/8.0/en/keyring-oci-plugin.html
No key information is permanently stored in MySQL server local storage. All keys are stored in Oracle Cloud Infrastructure Vault, making this plugin well suited for Oracle Cloud Infrastructure MySQL customers for management of their MySQL Enterprise ... Note The keyring_oci plugin is an extension included in MySQL Enterprise Edition, a commercial ...