content_image/664838.jpg content_image/664840.jpg content_image/664845.jpg
value, or until mysqld  is restarted. If the local value is set, the new value affects AUTO_INCREMENT columns for all tables into which new rows are inserted by the current user for the duration of the session, unless the values are changed during that session. 

The default value of auto_increment_increment  is 1. See Section 17.5.1.1, “Replication and AUTO_INCREMENT” . 

## • auto_increment_offset 

<img src='content_image/664838.jpg'>

This variable has a default value of 1. If it is left with its default value, and Group Replication is started on the server in multi-primary mode, it is changed to the server ID. For more information, see the description for auto_increment_increment . 

<img src='content_image/664840.jpg'>

## Note 

auto_increment_offset  is also supported for use with NDB  tables. 

As of MySQL 8.0.18, setting the session value of this system variable is no longer a restricted operation. 

## • immediate_server_version 

<img src='content_image/664845.jpg'>

For internal use by replication. This session system variable holds the MySQL Server release number of the server that is the immediate source in a replication topology (for example, 80014  for a MySQL 8.0.14 server instance). If this immediate server is at a release that does not support the session system variable, the value of the variable is set to 0 ( UNKNOWN_SERVER_VERSION ). 

The value of the variable is replicated from a source to a replica. With this information the replica can correctly process data originating from a source at an older release, by recognizing where syntax changes or semantic changes have occurred between the releases involved and handling these appropriately. The information can also be used in a Group Replication environment where one or more members of the replication group is at a newer release than the others. The value of the variable can be viewed in the binary log for each transaction (as part of the Gtid_log_event , 

