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/ndb-restore-to-different-version.html
A backup taken in NDB 8.0 of tables which were created in NDB 7.6 or earlier, and which have not been altered since upgrading to NDB 8.0, should be restorable to older versions of NDB Cluster. Such tables can be restored to an NDB 8.0 cluster, but ... The following two sections provide information about restoring a native NDB backup to a different version of NDB Cluster from the version in which the backup was ...
https://dev.mysql.com/doc/refman/8.0/en/nested-join-optimization.html
The following discussion refers to the join syntax described in Section 15.2.13.2, “JOIN Clause”. The syntax of table_factor is extended in comparison with the SQL Standard. The latter accepts only table_reference, not a list of them inside a ...
https://dev.mysql.com/doc/refman/8.0/en/not-enough-file-handles.html
If you get ERROR 'file_name' not found (errno: 23), Can't open file: file_name (errno: 24), or any other error with errno 23 or errno 24 from MySQL, it means that you have not allocated enough file descriptors for the MySQL server. If you have an ...You can either tell mysqld not to open so many files at once or increase the number of file descriptors available to ...
https://dev.mysql.com/doc/refman/8.0/en/operator-precedence.html
Operators that are shown together on a line have the same precedence. Operator precedences are shown in the following list, from highest precedence to the lowest. When used as a comparison operator, it has the same precedence as <=>, >=, >, <=, <, ...
https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html
After deleting a large part of a MyISAM or ARCHIVE table, or making many changes to a MyISAM or ARCHIVE table with variable-length rows (tables that have VARCHAR, VARBINARY, BLOB, or TEXT columns). OPTIMIZE TABLE reorganizes the physical storage of ...
https://dev.mysql.com/doc/refman/8.0/en/optimizer-issues.html
In many cases, MySQL can calculate the best possible query plan, but sometimes MySQL does not have enough information about the data at hand and has to make “educated” guesses about the data. For the cases when MySQL does not do the "right" ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-logging.html
Thus, if you have transactions that update, insert, or delete many rows, making the log buffer larger saves disk I/O. Setting the value too high may have a slight impact on fsync performance for log file writes due to several blocks being written at ... Consider the following guidelines for optimizing redo logging: Increase the size of your redo log ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-transaction-management.html
When rows are modified or deleted within a long-running transaction, other transactions using the READ COMMITTED and REPEATABLE READ isolation levels have to do more work to reconstruct the older data if they read those same rows. If secondary index ... To optimize InnoDB transaction processing, find the ideal balance between the performance overhead of transactional features and the workload of your ...
https://dev.mysql.com/doc/refman/8.0/en/option-modifiers.html
To disable column names, you can specify the option using any of these forms: --disable-column-names --skip-column-names --column-names=0 The --disable and --skip prefixes and the =0 suffix all have the same effect: They turn the option off. The ...
https://dev.mysql.com/doc/refman/8.0/en/out-of-range-and-overflow.html
If no restrictive modes are enabled, MySQL clips the value to the appropriate endpoint of the column data type range and stores the resulting value instead. When an out-of-range value is assigned to an integer column, MySQL stores the value ...