PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-intro.html
For example, you can change the port that memcached listens on, reduce the maximum number of simultaneous connections, change the maximum memory size for a key-value pair, or enable debugging messages for the error log. The InnoDB memcached plugin ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-replication.html
mysql> START SLAVE; Or from MySQL 8.0.22: mysql> START REPLICA; If the error log prints output similar to the following, the replica is ready for replication. Because the daemon_memcached plugin supports the MySQL binary log, source server through ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-security.html
memcp --servers=localhost:11211 --binary --username=testname --password=password myfile.txt memcat --servers=localhost:11211 --binary --username=testname --password=password myfile.txt If you specify an incorrect user name or password, the operation ... Caution Consult this section before deploying the daemon_memcached plugin on a production server, or even on a test server if the MySQL instance contains sensitive ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-tuning.html
In case of an outage, a maximum of 100 records are lost, which may be an acceptable margin of error. Because using InnoDB in combination with memcached involves writing all data to disk, whether immediately or sometime later, raw performance is ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-moving-data-files-offline.html
If duplicate tablespace files are discovered by the scan, startup fails with an error indicating that multiple files were found for the same tablespace ID. The innodb_directories variable, which defines directories to scan at startup for tablespace ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-failure-conditions.html
The failure of an online DDL operation is typically due to one of the following conditions: An ALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine. A LOCK clause specifies a low ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-performance.html
If the LOCK clause specifies a less restrictive level of locking than is permitted for a particular DDL operation, the statement fails with an error. Online DDL improves several aspects of MySQL operation: Applications that access the table are ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-optimize-tablespace-page-allocation.html
Attempting to disable innodb_extend_and_initialize on those systems returns the following error: Changing innodb_extend_and_initialize not supported on this platform. As of MySQL 8.0.22, you can optimize how InnoDB allocates space to file-per-table ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-page-compression.html
Loading a page-compressed tablespace on a server that does not support the compression algorithm that was used causes an I/O error. InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is ...