mirror of
https://github.com/MariaDB/server.git
synced 2025-11-30 05:23:50 +03:00
b1b2689f17
This patch changes statement rollback for streaming replication. Previously, a statement rollback was turned into full transaction rollback in the case where the transaction had already replicated a fragment. This was introduced in the initial implementation of streaming replication due to the fact that we do not have a mechanism to perform a statement rollback on the applying side. This policy is however overly pessimistic, causing full rollbacks even in cases where a local statement rollback, would not require a statement rollback on the applying side. This happens to be case when the statement itself has not replicated any fragments. So the patch changes the condition that determines if a statement rollback should be turned into a full rollback accordingly. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
22 lines
590 B
Plaintext
22 lines
590 B
Plaintext
#
|
|
# Statement with no side effects causes unnecessary full rollback
|
|
#
|
|
|
|
--source include/galera_cluster.inc
|
|
|
|
CREATE TABLE t1 (f1 INTEGER PRIMARY KEY);
|
|
SET SESSION wsrep_trx_fragment_size=1;
|
|
START TRANSACTION;
|
|
INSERT INTO t1 VALUES (1);
|
|
# Let's cause some bogus error with a statement that
|
|
# does not cause any replication event.
|
|
# The following used to return error ER_LOCK_DEADLOCK
|
|
# and cause the entire transaction to be rolled back.
|
|
--error ER_GLOBAL_VARIABLE
|
|
SET SESSION wsrep_cluster_name = ' ';
|
|
|
|
INSERT INTO t1 VALUES (2);
|
|
COMMIT;
|
|
|
|
SELECT f1 AS expect_1_and_2 FROM t1;
|
|
DROP TABLE t1; |