PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.1Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/gtid-functions.html
Table 14.26 GTID Functions Name Description Deprecated GTID_SUBSET() Return true if all GTIDs in subset are also in set; otherwise false. The functions described in this section are used with GTID-based replication. It is important to keep in mind ...
https://dev.mysql.com/doc/refman/8.0/en/hexadecimal-literals.html
Hexadecimal literal values are written using X'val' or 0xval notation, where val contains hexadecimal digits (0..9, A..F). Lettercase of the digits and of any leading X does not matter. A leading 0x is case-sensitive and cannot be written as 0X.
https://dev.mysql.com/doc/refman/8.0/en/history.html
We started out with the intention of using the mSQL database system to connect to our tables using our own fast low-level (ISAM) routines. However, after some testing, we came to the conclusion that mSQL was not fast enough or flexible enough for ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-adaptive-hash.html
If a table fits almost entirely in main memory, a hash index speeds up queries by enabling direct lookup of any element, turning the index value into a sort of pointer. The adaptive hash index enables InnoDB to perform more like an in-memory ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-autocommit-commit-rollback.html
$> mysql test mysql> CREATE TABLE customer (a INT, b CHAR (20), INDEX (a)); Query OK, 0 rows affected (0.00 sec) mysql> -- Do a transaction with autocommit turned on. If autocommit mode is enabled, each SQL statement forms a single transaction on ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-check-availability.html
Issue the SHOW ENGINES statement to view the available MySQL storage engines.
https://dev.mysql.com/doc/refman/8.0/en/innodb-error-handling.html
If you run out of file space in a tablespace, a MySQL Table is full error occurs and InnoDB rolls back the SQL statement. InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. A transaction ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-tuning.html
For other ways to reduce or tune I/O for table operations, see Section 10.5.8, “Optimizing InnoDB Disk I/O”. Increase the setting when processing large numbers of updates intended only for statistical analysis, where losing the last N updates in ... Because using InnoDB in combination with memcached involves writing all data to disk, whether immediately or sometime later, raw performance is expected to be somewhat slower than using memcached by ...
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-optimize-tablespace-page-allocation.html
As of MySQL 8.0.22, you can optimize how InnoDB allocates space to file-per-table and general tablespaces on Linux. By default, when additional space is required, InnoDB allocates pages to the tablespace and physically writes NULLs to those pages.