PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-features-row-searches.html
A unique index where every column in the index has a NOT NULL attribute. If the algorithm is able to select a primary key or a unique index where every column in the index has a NOT NULL attribute, it uses this index to iterate over the rows in the ... When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-concepts.html
A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the source). This identifier is unique not only to the server on which it originated, but is unique across ...GTID assignment distinguishes between client transactions, which are committed on the source, and replicated transactions, which are reproduced on a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-additionalslaves.html
On the new replica, edit the configuration and give the new replica a unique server ID (using the server_id system variable) that is not used by the source or any of the existing replicas. Also display the server ID and server UUID and verify that ... You can add another replica to an existing replication configuration without stopping the source ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-slavebaseconfig.html
Each replica must have a unique server ID, as specified by the server_id system variable. If you are setting up multiple replicas, each one must have a unique server_id value that differs from that of the source and from any of the other replicas.
https://dev.mysql.com/doc/refman/8.0/en/replication-options.html
For servers that are used in a replication topology, you must specify a unique server ID for each replication server, in the range from 1 to 232 − 1. “Unique” means that each ID must be different from every other ID in use by any other source ... The following sections contain information about mysqld options and server variables that are used in replication and for controlling the binary ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html
ON DUPLICATE KEY UPDATE statements on tables with multiple primary or unique keys. When executed against a table that contains more than one primary or unique key, this statement is considered unsafe, being sensitive to the order in which the ...
https://dev.mysql.com/doc/refman/8.0/en/show-replicas.html
Source_id: The unique server ID of the source server that the replica server is replicating from. Replica_UUID: The globally unique ID of this replica, as generated on the replica and found in the replica's auto.cnf file. {SHOW REPLICAS} Displays a ...
https://dev.mysql.com/doc/refman/8.0/en/timestamp-lookups.html
For example: SET time_zone = 'MET'; Unique UTC values stored in the TIMESTAMP column are not unique in the session time zone due to DST shifts. If the index is not UNIQUE, it is possible for the table (and the index) to store multiple instances of a ... Temporal values are stored in TIMESTAMP columns as UTC values, and values inserted into and retrieved from TIMESTAMP columns are converted between the session time zone and ...
https://dev.mysql.com/doc/refman/8.0/en/x-plugin-options-system-variables.html
mysqlx_document_id_unique_prefix Command-Line Format --mysqlx-document-id-unique-prefix=# System Variable mysqlx_document_id_unique_prefix Scope Global Dynamic Yes SET_VAR Hint Applies No Type Integer Default Value 0 Minimum Value 0 Maximum Value ...
https://dev.mysql.com/doc/refman/8.0/en/xa-statements.html
Each XA transaction must have a unique xid value, so the value must not currently be used by another XA transaction. For this reason, gtrid values must be globally unique so that there is no ambiguity about which global transaction a given XA ... To ...