XA operations do not take global commit lock under LOCK TABLES FOR BACKUP

[Yura Sorokin]

In 5.7.19 Oracle fixed Bug #84442 "XA PREPARE inconsistent with XTRABACKUP"
(https://bugs.mysql.com/bug.php?id=84442).
XA PREPARE, XA ROLLBACK, and XA COMMIT for a transaction from a
disconnected session did not take a global commit lock and modified
the binary log and InnoDB redo log even when FLUSH TABLES WITH READ
LOCK was in effect. This could lead to inconsistent backups when
backup tools assumed that the server was in a read-only state.

Similar changes must be implemented for Percona-specific LOCK TABLES FOR BACKUP / LOCK BINLOG FOR BACKUP.

In the following MTR test case fragment "xa prepare 'test1'" must fail with ER_LOCK_WAIT_TIMEOUT.

--echo # Check XA state when lock_wait_timeout happens
--echo # More tests added to flush_read_lock.test
connect (con_tmp,localhost,root,,);
set session lock_wait_timeout=1;
create table asd (a int);
xa start 'test1';
insert into asd values(1);
xa end 'test1';
connection default;

lock tables for backup;

connection con_tmp;
--echo # PREPARE error will do auto rollback.
--ERROR ER_LOCK_WAIT_TIMEOUT
xa prepare 'test1';
show errors;
connection default;
unlock tables;

[Yura Sorokin (yura-sorokin)]

The full set of test cases can be found in Oracle's commit 25106b8
"Bug 25364178 - XA PREPARE INCONSISTENT WITH XTRABACKUP"
https://github.com/mysql/mysql-server/commit/25106b8

[Yura Sorokin (yura-sorokin)]

See also bug 1651941

[Sveta Smirnova (svetasmirnova)]

Thank you for the report.

Verified as described.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1817