mariadb/mysql-test/suite/binlog/t/binlog_1pc.test
Andrei 5bf4dee369 MDEV-28948 FLUSH BINARY LOGS waits/hangs on mysql_mutex_unlock(&LOCK_index)
The hang may be caused by a 1pc branch that was fixed by MDEV-26031 in
10.6 and up. That commit did not look relevant in 10.5 and below
so  was not pushed to the low branches.

To possibly tackle the reported issue
the MDEV-26031 is backported now with a test that
unlike 10.6 does not expose the former bug in 10.5.
It is only needed for checking a refined logics
inside MYSQL_BIN_LOG::write_transaction_to_binlog.
The latter is made to do away with xid-unlogging (which is suspected
to have been at fault) for xid-less transaction.
2022-07-26 10:46:01 +03:00

39 lines
1.1 KiB
Text

# The test file contains tests specific to one phase commit
# execution and binlogging.
#
# MDEV-26031 unnessary xid logging in one phase commit case
#
--source include/have_innodb.inc
--source include/have_aria.inc
--source include/have_binlog_format_mixed.inc
RESET MASTER;
CREATE TABLE t (f INT) ENGINE=INNODB;
CREATE TABLE ta (f INT) ENGINE=Aria;
--let $binlog_start = query_get_value(SHOW MASTER STATUS, Position, 1)
BEGIN;
INSERT INTO t SET f = 1;
INSERT INTO ta SET f = 1;
COMMIT;
--let $binlog_file = query_get_value(SHOW MASTER STATUS, File, 1)
--source include/show_binlog_events.inc
--echo # Prove that binlog is resettable. Under the bug condition it was not.
RESET MASTER;
--let $binlog_start = query_get_value(SHOW MASTER STATUS, Position, 1)
--let $binlog_file = query_get_value(SHOW MASTER STATUS, File, 1)
SET @@binlog_format = ROW;
CREATE TABLE ta2 ENGINE = Aria SELECT * from t;
--source include/show_binlog_events.inc
--echo # Prove that binlog is resettable. Under the bug condition it was not.
RESET MASTER;
--echo # Cleanup
DROP TABLE ta2, ta, t;
--echo # End of the tests