mirror of
https://github.com/MariaDB/server.git
synced 2025-05-05 16:59:35 +03:00
ee2b7db3f8
When @@GLOBAL.gtid_strict_mode=1, then certain operations result in error that would otherwise result in out-of-order binlog files between servers. GTID sequence numbers are now allocated independently per domain; this results in less/no holes in GTID sequences, increasing the likelyhood that diverging binlogs will be caught by the slave when GTID strict mode is enabled.
22 lines
697 B
Plaintext
22 lines
697 B
Plaintext
--source include/not_embedded.inc
|
|
#
|
|
# only global
|
|
#
|
|
select @@global.gtid_strict_mode;
|
|
--error ER_INCORRECT_GLOBAL_LOCAL_VAR
|
|
select @@session.gtid_strict_mode;
|
|
show global variables like 'gtid_strict_mode';
|
|
show session variables like 'gtid_strict_mode';
|
|
select * from information_schema.global_variables where variable_name='gtid_strict_mode';
|
|
select * from information_schema.session_variables where variable_name='gtid_strict_mode';
|
|
|
|
SET @old= @@GLOBAL.gtid_strict_mode;
|
|
set global gtid_strict_mode=1;
|
|
select @@global.gtid_strict_mode;
|
|
set global gtid_strict_mode=0;
|
|
select @@global.gtid_strict_mode;
|
|
set global gtid_strict_mode=@old;
|
|
|
|
--error ER_GLOBAL_VARIABLE
|
|
set session gtid_strict_mode=1;
|