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/xa-restrictions.html
Also, with the replica's connection metadata repository and applier metadata repository stored in InnoDB tables, which became the default in MySQL 8.0, the internal state of the data engine transaction is changed following a filtered XA transaction, ... XA transaction support is limited to the InnoDB storage ...For “Internal XA”, storage engines ...For ...
https://dev.mysql.com/doc/refman/8.0/en/switchable-optimizations.html
Specifying any given opt_name more than once in the value is not permitted and causes an error. Any errors in the value cause the assignment to fail with an error, leaving the value of optimizer_switch unchanged. For batched_key_access to have any ...Its value is a set of flags, each of which has a value of on or off to indicate whether the corresponding optimizer behavior is enabled or ...
https://dev.mysql.com/doc/refman/8.0/en/creating-spatial-columns.html
Columns with a spatial data type can have an SRID attribute, to explicitly indicate the spatial reference system (SRS) for values stored in the column. Spatial columns are supported for MyISAM, InnoDB, NDB, and ARCHIVE tables. See also the notes ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication.html
Normal (non-clustered) replication involves a source server and a replica server, the source being so named because operations and data to be replicated originate with it, and the replica being the recipient of these. We refer to the MySQL source ...
https://dev.mysql.com/doc/refman/8.0/en/optimize-blob.html
Do not use this technique when the entire table is compressed by InnoDB or MyISAM. Since the performance requirements to retrieve and display a BLOB value might be very different from other data types, you could put the BLOB-specific table on a ...
https://dev.mysql.com/doc/refman/8.0/en/descending-indexes.html
For InnoDB full-text search, this means that the index required on the FTS_DOC_ID column of the indexed table cannot be defined as a descending index. Descending indexes also make it possible for the optimizer to use multiple-column indexes when the ... MySQL supports descending indexes: DESC in an index definition is no longer ignored but causes storage of key values in descending ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-types.html
These columns can contain other than integer values, since the hashing function supplied by MySQL guarantees an integer result regardless of the column data type. For HASH partitioning, the user-supplied expression must evaluate to an integer value.
https://dev.mysql.com/doc/refman/8.0/en/values.html
Each ROW() in the same VALUES statement must have the same number of values in its value list. The DEFAULT keyword is not supported by VALUES and causes a syntax error, except when it is used to supply values in an INSERT statement. The constructed ...In other words, it is a table value constructor which also functions as a standalone SQL ... VALUES is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterbaseconfig.html
Note The following options also have an impact on the source: For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should use innodb_flush_log_at_trx_commit=1 and sync_binlog=1 in the ... To ...Otherwise, a server restart is not needed when you change the server ID, unless you make other configuration changes that require ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
If under row-based replication the replica applied the triggers as well as the row changes caused by them, the changes would in effect be applied twice on the replica, leading to different data on the source and the replica. If you want triggers to ... With statement-based replication, triggers executed on the source also execute on the ...However, to ...