Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html
The use of the AUTO_INCREMENT modifier with FLOAT and DOUBLE columns in CREATE TABLE and ALTER TABLE statements was deprecated in MySQL 8.0; support for it is removed altogether in MySQL 8.4, where it raises ER_WRONG_FIELD_SPEC (Incorrect column ...
https://dev.mysql.com/doc/refman/8.4/en/prepare.html
If auto-reconnect is enabled, the client is not notified that the connection was lost. For some combinations of actual type and derived type, an automatic repreparation of the statement is triggered, to ensure closer compatibility with previous ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
The auto-skip function for GTIDs means that a transaction committed on the source can be applied no more than once on the replica, which helps to guarantee consistency. If the first attempt committed, all the concurrent sessions stop being blocked, ... A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-lifecycle.html
If the GTID has already been used, no error is raised, and the auto-skip function is used to ignore the transaction. It also ensures that the filtered-out transactions are not retrieved again if the replica reconnects to the source, as explained in ... The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids.html
The auto-positioning function for synchronizing a replica and source that use GTIDs (see Section 19.1.3.3, “GTID Auto-Positioning”). This section explains transaction-based replication using global transaction identifiers (GTIDs). Because ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-channel-based-filters.html
This happens so that a replica’s GTID set stays consistent with the source’s, meaning GTID auto-positioning can be used without re-acquiring filtered out transactions each time. The second channel to attempt it skips the transaction using GTID ... This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication ...
https://dev.mysql.com/doc/refman/8.4/en/show-replica-status.html
The file position (Relay_Log_Pos) is set to position 4, and GTID auto-skip is used to skip any transactions in the file that were already applied. Auto_Position 1 if GTID auto-positioning is in use for the channel, otherwise 0. SHOW REPLICA STATUS ...
https://dev.mysql.com/doc/refman/8.4/en/upgrading-what-is-upgraded.html
The --upgrade server option controls whether and how the server performs an automatic upgrade at startup: With no option or with --upgrade=AUTO, the server upgrades anything it determines to be out of date (steps 1 and 2). One way that FORCE differs ... Installing a new version of MySQL may require upgrading these parts of the existing installation: The mysql system schema, which contains tables that store information required by the MySQL server as it runs (see Section 7.3, “The mysql System ...
https://dev.mysql.com/doc/refman/8.4/en/using-system-variables.html
The MySQL server maintains many system variables that configure its operation. Section 7.1.8, “Server System Variables”, describes the meaning of these variables. System variables can be set at server startup using options on the command line ...
https://dev.mysql.com/doc/relnotes/mysql-cluster-manager/8.4/en/news-8-4-0.html
(Bug #36398066, Bug #36210786) Client: Auto completion for client commands did not always work. To enable the function, use the --auto-rehash variable to TRUE when you start the mcm client. MySQL Cluster Manager 8.4.0 marks the start of a new ...