PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 296.4Kb
Man Pages (Zip)
- 401.7Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysqlbinlog.html
If the binary log was written by a mysqld with server-id-bits set to less than 32 and user data stored in the most significant bit, running mysqlbinlog with --server-id-bits set to 32 enables this data to be seen. The server's binary log consists ...
https://dev.mysql.com/doc/refman/8.0/en/mysqldump-definition-data-dumps.html
The --no-data option tells mysqldump not to dump table data, resulting in the dump file containing only statements to create the tables. Conversely, the --no-create-info option tells mysqldump to suppress CREATE statements from the output, so that ...
https://dev.mysql.com/doc/refman/8.0/en/mysqlslap.html
mysqlslap runs in three stages: Create schema, table, and optionally any stored programs or data to use for the test. mysqlslap is a diagnostic program designed to emulate client load for a MySQL server and to report the timing of each stage.
https://dev.mysql.com/doc/refman/8.0/en/numeric-types.html
The BIT data type stores bit values and is supported for MyISAM, MEMORY, InnoDB, and NDB tables. These types include the exact numeric data types (INTEGER, SMALLINT, DECIMAL, and NUMERIC), as well as the approximate numeric data types (FLOAT, REAL, ...
https://dev.mysql.com/doc/refman/8.0/en/optimize-character.html
When consecutive primary values are physically stored near each other, InnoDB can insert and retrieve them faster. For character and string columns, follow these guidelines: Use binary collation order for fast comparison and sort operations, when ...
https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html
InnoDB stores data using a page-allocation method and does not suffer from fragmentation in the same way that legacy storage engines (such as MyISAM) do. OPTIMIZE TABLE reorganizes the physical storage of table data and associated index data, to ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-configuration-variables.html
You might change this setting during periods of unusual activity, then restore it to its original setting. Preventing one-time operations such as table scans from interfering with the frequently accessed data stored in the InnoDB buffer cache.
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-many-tables.html
If you have configured non-persistent optimizer statistics (a non-default configuration), InnoDB computes index cardinality values for a table the first time that table is accessed after startup, instead of storing such values in the table. This ...
https://dev.mysql.com/doc/refman/8.0/en/out-of-memory.html
Is it reasonable that it should return so many rows? If not, correct the query and try again. This causes it to use the mysql_use_result() C API function to retrieve the result set, which places less of a load on the client (but more on the server).
https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-list.html
This is a variant of LIST partitioning that enables the use of multiple columns as partition keys, and for columns of data types other than integer types to be used as partitioning columns; you can use string types, DATE, and DATETIME columns. In ...