We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[--] Binary logging is enabled (GTID MODE: OFF)
while in fact gtid is enabled and in use:
MariaDB [(none)]> show variables like '%gtid%'; +-------------------------+----------------------------------------+ | Variable_name | Value | +-------------------------+----------------------------------------+ | gtid_binlog_pos | 253-253-2941486643,254-254-31282069900 | | gtid_binlog_state | 253-253-2941486643,254-254-31282069900 | | gtid_cleanup_batch_size | 64 | | gtid_current_pos | 253-253-2941486643,254-254-31282069900 | | gtid_domain_id | 254 | | gtid_ignore_duplicates | ON | | gtid_pos_auto_engines | | | gtid_seq_no | 0 | | gtid_slave_pos | 253-253-2941486643,254-254-31282069900 | | gtid_strict_mode | OFF | | last_gtid | | | wsrep_gtid_domain_id | 0 | | wsrep_gtid_mode | OFF | +-------------------------+----------------------------------------+ 13 rows in set (0.001 sec)
The text was updated successfully, but these errors were encountered:
mariadb gtid mode - base off gtid_current_pos.
9d1d19c
gtid_strict_mode isn't sufficient a test for MariaDB's GTID mode. The gtid_current_pos however is always non-blank if GTID is enabled. closes major#513
Successfully merging a pull request may close this issue.
[--] Binary logging is enabled (GTID MODE: OFF)
while in fact gtid is enabled and in use:
The text was updated successfully, but these errors were encountered: