mirror of
https://github.com/MariaDB/server.git
synced 2025-09-09 18:40:27 +03:00
cd1a11ace3
While sql_bin_log=1(0) is meant to control binary logging for the current session so that the updates to do(not) get logged into the binary log to be replicated to the async MariaDB slave. The same should not affect galera replication. That is, the updates should always get replicated to other galera nodes regardless of sql_bin_log's value. Fixed by making sure that the updates are written to binlog cache irrespective of sql_bin_log. Added test cases.
27 lines
539 B
Plaintext
27 lines
539 B
Plaintext
#
|
|
# Test SET SESSION sql_log_bin = 0 . We expect that updates gets repliated to
|
|
# other nodes while they do not show up in the binary log files.
|
|
# (see galera.galera_as_master)
|
|
#
|
|
|
|
--source include/galera_cluster.inc
|
|
--source include/have_innodb.inc
|
|
|
|
CREATE TABLE t1 (f1 INTEGER) ENGINE=InnoDB;
|
|
|
|
SET SESSION sql_log_bin = 0;
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
SET SESSION sql_log_bin = 1;
|
|
|
|
INSERT INTO t1 VALUES (2);
|
|
|
|
|
|
--connection node_2
|
|
SELECT COUNT(*) = 2 FROM t1;
|
|
SELECT COUNT(*) = 1 FROM t1 WHERE f1 = 1;
|
|
|
|
--connection node_1
|
|
DROP TABLE t1;
|