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/optimizing-innodb-bulk-data-loading.html
When performing bulk inserts, it is faster to insert rows in PRIMARY KEY order. InnoDB tables use a clustered index, which makes it relatively fast to use data in the order of the PRIMARY KEY. Performing bulk inserts in PRIMARY KEY order is ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-queries-myisam.html
This is a good way to make queries faster if you have a unique index from which you want to read all rows in order according to the index. Some general tips for speeding up queries on MyISAM tables: To help MySQL better optimize queries, use ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-limitations.html
ORDER BY column statement run against a partitioned table causes ordering of rows only within each partition. This section discusses current restrictions and limitations on MySQL partitioning support. The following constructs are not permitted in ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-quick-start.html
This section briefly introduces the Performance Schema with examples that show how to use it. For additional examples, see Section 29.19, “Using the Performance Schema to Diagnose Problems”. To enable or disable it explicitly, start the server ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-variables-info-table.html
The variables_info table shows, for each system variable, the source from which it was most recently set, and its range of values. VARIABLE_SOURCE The source from which the variable was most recently set: COMMAND_LINE The variable was set on the ...
https://dev.mysql.com/doc/refman/8.0/en/problems-with-null.html
When using DISTINCT, GROUP BY, or ORDER BY, all NULL values are regarded as equal. When using ORDER BY, NULL values are presented first, or last if you specify DESC to sort in descending order. The concept of the NULL value is a common source of ...
https://dev.mysql.com/doc/refman/8.0/en/query-log.html
mysqld writes statements to the query log in the order that it receives them, which might differ from the order in which they are executed. This logging order is in contrast with that of the binary log, for which statements are written after they ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-limit.html
SELECT statements is unsafe since the order of the rows affected is not defined. (Such statements can be replicated correctly with statement-based replication only if they also contain an ORDER BY clause.) When such a statement is encountered: When ... Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-assign-anon.html
On a multi-threaded replica, this means the order of the GTIDs does not necessarily match the order of the transactions, even if slave-preserve-commit-order=1 is set. From MySQL 8.0.23, you can set up replication channels to assign a GTID to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-concepts.html
The transaction_id is a sequence number determined by the order in which the transaction was committed on the source. This example shows the GTID set stored in the gtid_executed system variable (@@GLOBAL.gtid_executed) of a replica that has applied ... A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the ...