PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/mysqlbinlog-row-events.html
Omitting extraneous lines, the output for the row events produced by the preceding statement sequence looks like this: $> mysqlbinlog log_file ... This is similar to --base64-output=NEVER but does not exit with an error if a row event is found. If ... The following examples illustrate how mysqlbinlog displays row events that specify data ...
https://dev.mysql.com/doc/refman/5.7/en/nested-loop-joins.html
This process is repeated as many times as there remain tables to be joined. This reduces by an order of magnitude the number of times the inner table must be read. MySQL executes joins between tables using a nested-loop algorithm or variations on ...
https://dev.mysql.com/doc/refman/5.7/en/nontransactional-tables.html
If you were not deliberately mixing transactional and nontransactional tables within the transaction, the most likely cause for this message is that a table you thought was transactional actually is not. This can happen if you try to create a table ... If you receive the following message when trying to perform a ROLLBACK, it means that one or more of the tables you used in the transaction do not support transactions: Warning: Some non-transactional changed tables couldn't be rolled back These nontransactional tables are not affected by the ROLLBACK ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-transaction-management.html
To minimize the chance of this issue occurring: Increase the size of the buffer pool so that all the data change changes can be cached rather than immediately written to disk. This issue is expected to be infrequent with the default setting ... To ...
https://dev.mysql.com/doc/refman/5.7/en/option-modifiers.html
To do this, use a --maximum prefix with the variable name. For example, with --maximum-back_log=200, the server produces this error: Maximum value of 'back_log' cannot be set . Some options are “boolean” and control behavior that can be turned ...
https://dev.mysql.com/doc/refman/5.7/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 ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-functions.html
This section discusses limitations in MySQL Partitioning relating specifically to functions used in partitioning expressions. For this reason, EXTRACT() is not permitted as a partitioning function when it specifies the unit as WEEK. Each of these ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-locking.html
For statements affecting partitioned tables using storage engines such as InnoDB, that employ row-level locking and do not actually perform (or need to perform) the locks prior to partition pruning, this is not an issue. In MySQL 5.7, partition lock ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-atom-molecule-events.html
For example, a row fetch might result in rows like this: Row# EVENT_NAME TIMER_START TIMER_END ---- ---------- ----------- --------- 1 wait/io/file/myisam/dfile 10001 10002 2 wait/io/table/sql/handler 10000 NULL The row fetch causes a file read.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-connection-attribute-tables.html
This convention permits new attributes to be introduced by MySQL without colliding with application attributes, and enables application programs to define their own attributes that do not collide with internal attributes. For connections initiated ... Connection attributes are key-value pairs that application programs can pass to the server at connect ...