2015-04-09 08:13:07 +03:00
|
|
|
--source include/have_innodb.inc
|
2015-04-09 16:43:33 +03:00
|
|
|
# Embedded server does not support restarting.
|
|
|
|
|
--source include/not_embedded.inc
|
2022-07-01 14:42:13 +03:00
|
|
|
--source include/no_valgrind_without_big.inc
|
2015-04-09 08:13:07 +03:00
|
|
|
|
2015-09-24 21:24:28 +03:00
|
|
|
# MDEV-8841 - close tables opened by previous tests,
|
|
|
|
|
# so they don't get marked crashed when the server gets crashed
|
|
|
|
|
--disable_query_log
|
2020-06-05 14:59:33 +03:00
|
|
|
call mtr.add_suppression("Found [12] prepared XA transactions");
|
2015-09-24 21:24:28 +03:00
|
|
|
FLUSH TABLES;
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
2024-05-21 09:52:35 +03:00
|
|
|
CREATE TABLE t1 (a INT PRIMARY KEY) ENGINE=InnoDB;
|
2015-04-09 08:13:07 +03:00
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
|
connect (con1,localhost,root);
|
|
|
|
|
XA START 'x'; UPDATE t1 set a=2; XA END 'x'; XA PREPARE 'x';
|
2020-06-05 14:59:33 +03:00
|
|
|
connect (con2,localhost,root);
|
2024-05-21 09:52:35 +03:00
|
|
|
CREATE TABLE t2 (a INT PRIMARY KEY) ENGINE=InnoDB;
|
2020-06-05 14:59:33 +03:00
|
|
|
XA START 'y'; INSERT INTO t2 VALUES (1); XA END 'y'; XA PREPARE 'y';
|
2015-04-09 08:13:07 +03:00
|
|
|
connection default;
|
|
|
|
|
|
2017-08-23 13:03:13 +03:00
|
|
|
# innodb_force_recovery=2 prevents the purge and tests that the fix of
|
|
|
|
|
# MDEV-13606 XA PREPARE transactions should survive innodb_force_recovery=1 or 2
|
|
|
|
|
# is present.
|
|
|
|
|
--let $restart_parameters= --innodb-force-recovery=2
|
2017-03-12 11:18:51 +01:00
|
|
|
--let $shutdown_timeout=0
|
|
|
|
|
--source include/restart_mysqld.inc
|
2017-08-23 13:03:13 +03:00
|
|
|
--let $restart_parameters=
|
2017-08-29 10:07:33 +03:00
|
|
|
--let $shutdown_timeout=
|
2015-04-09 08:13:07 +03:00
|
|
|
|
|
|
|
|
disconnect con1;
|
2020-06-05 14:59:33 +03:00
|
|
|
disconnect con2;
|
2015-04-09 08:13:07 +03:00
|
|
|
connect (con1,localhost,root);
|
|
|
|
|
--send SELECT * FROM t1 LOCK IN SHARE MODE
|
|
|
|
|
|
|
|
|
|
connection default;
|
|
|
|
|
let $wait_condition=
|
|
|
|
|
select count(*) = 1 from information_schema.processlist
|
|
|
|
|
where state = 'Sending data' and
|
|
|
|
|
info = 'SELECT * FROM t1 LOCK IN SHARE MODE';
|
|
|
|
|
--source include/wait_condition.inc
|
|
|
|
|
|
MDEV-25506 (3 of 3): Do not delete .ibd files before commit
This is a complete rewrite of DROP TABLE, also as part of other DDL,
such as ALTER TABLE, CREATE TABLE...SELECT, TRUNCATE TABLE.
The background DROP TABLE queue hack is removed.
If a transaction needs to drop and create a table by the same name
(like TRUNCATE TABLE does), it must first rename the table to an
internal #sql-ib name. No committed version of the data dictionary
will include any #sql-ib tables, because whenever a transaction
renames a table to a #sql-ib name, it will also drop that table.
Either the rename will be rolled back, or the drop will be committed.
Data files will be unlinked after the transaction has been committed
and a FILE_RENAME record has been durably written. The file will
actually be deleted when the detached file handle returned by
fil_delete_tablespace() will be closed, after the latches have been
released. It is possible that a purge of the delete of the SYS_INDEXES
record for the clustered index will execute fil_delete_tablespace()
concurrently with the DDL transaction. In that case, the thread that
arrives later will wait for the other thread to finish.
HTON_TRUNCATE_REQUIRES_EXCLUSIVE_USE: A new handler flag.
ha_innobase::truncate() now requires that all other references to
the table be released in advance. This was implemented by Monty.
ha_innobase::delete_table(): If CREATE TABLE..SELECT is detected,
we will "hijack" the current transaction, drop the table in
the current transaction and commit the current transaction.
This essentially fixes MDEV-21602. There is a FIXME comment about
making the check less failure-prone.
ha_innobase::truncate(), ha_innobase::delete_table():
Implement a fast path for temporary tables. We will no longer allow
temporary tables to use the adaptive hash index.
dict_table_t::mdl_name: The original table name for the purpose of
acquiring MDL in purge, to prevent a race condition between a
DDL transaction that is dropping a table, and purge processing
undo log records of DML that had executed before the DDL operation.
For #sql-backup- tables during ALTER TABLE...ALGORITHM=COPY, the
dict_table_t::mdl_name will differ from dict_table_t::name.
dict_table_t::parse_name(): Use mdl_name instead of name.
dict_table_rename_in_cache(): Update mdl_name.
For the internal FTS_ tables of FULLTEXT INDEX, purge would
acquire MDL on the FTS_ table name, but not on the main table,
and therefore it would be able to run concurrently with a
DDL transaction that is dropping the table. Previously, the
DROP TABLE queue hack prevented a race between purge and DDL.
For now, we introduce purge_sys.stop_FTS() to prevent purge from
opening any table, while a DDL transaction that may drop FTS_
tables is in progress. The function fts_lock_table(), which will
be invoked before the dictionary is locked, will wait for
purge to release any table handles.
trx_t::drop_table_statistics(): Drop statistics for the table.
This replaces dict_stats_drop_index(). We will drop or rename
persistent statistics atomically as part of DDL transactions.
On lock conflict for dropping statistics, we will fail instantly
with DB_LOCK_WAIT_TIMEOUT, because we will be holding the
exclusive data dictionary latch.
trx_t::commit_cleanup(): Separated from trx_t::commit_in_memory().
Relax an assertion around fts_commit() and allow DB_LOCK_WAIT_TIMEOUT
in addition to DB_DUPLICATE_KEY. The call to fts_commit() is
entirely misplaced here and may obviously break the consistency
of transactions that affect FULLTEXT INDEX. It needs to be fixed
separately.
dict_table_t::n_foreign_key_checks_running: Remove (MDEV-21175).
The counter was a work-around for missing meta-data locking (MDL)
on the SQL layer, and not really needed in MariaDB.
ER_TABLE_IN_FK_CHECK: Replaced with ER_UNUSED_28.
HA_ERR_TABLE_IN_FK_CHECK: Remove.
row_ins_check_foreign_constraints(): Do not acquire
dict_sys.latch either. The SQL-layer MDL will protect us.
This was reviewed by Thirunarayanan Balathandayuthapani
and tested by Matthias Leich.
2021-06-09 17:02:55 +03:00
|
|
|
SET innodb_lock_wait_timeout=1;
|
|
|
|
|
--error ER_LOCK_WAIT_TIMEOUT
|
2020-06-05 14:59:33 +03:00
|
|
|
DROP TABLE t2;
|
|
|
|
|
|
2015-04-09 08:13:07 +03:00
|
|
|
disconnect con1;
|
|
|
|
|
|
|
|
|
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
2023-05-31 11:57:45 +07:00
|
|
|
--disable_ps2_protocol
|
2015-04-09 08:13:07 +03:00
|
|
|
SELECT * FROM t1;
|
2023-05-31 11:57:45 +07:00
|
|
|
--enable_ps2_protocol
|
2015-04-09 08:13:07 +03:00
|
|
|
XA ROLLBACK 'x';
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
MDEV-25506 (3 of 3): Do not delete .ibd files before commit
This is a complete rewrite of DROP TABLE, also as part of other DDL,
such as ALTER TABLE, CREATE TABLE...SELECT, TRUNCATE TABLE.
The background DROP TABLE queue hack is removed.
If a transaction needs to drop and create a table by the same name
(like TRUNCATE TABLE does), it must first rename the table to an
internal #sql-ib name. No committed version of the data dictionary
will include any #sql-ib tables, because whenever a transaction
renames a table to a #sql-ib name, it will also drop that table.
Either the rename will be rolled back, or the drop will be committed.
Data files will be unlinked after the transaction has been committed
and a FILE_RENAME record has been durably written. The file will
actually be deleted when the detached file handle returned by
fil_delete_tablespace() will be closed, after the latches have been
released. It is possible that a purge of the delete of the SYS_INDEXES
record for the clustered index will execute fil_delete_tablespace()
concurrently with the DDL transaction. In that case, the thread that
arrives later will wait for the other thread to finish.
HTON_TRUNCATE_REQUIRES_EXCLUSIVE_USE: A new handler flag.
ha_innobase::truncate() now requires that all other references to
the table be released in advance. This was implemented by Monty.
ha_innobase::delete_table(): If CREATE TABLE..SELECT is detected,
we will "hijack" the current transaction, drop the table in
the current transaction and commit the current transaction.
This essentially fixes MDEV-21602. There is a FIXME comment about
making the check less failure-prone.
ha_innobase::truncate(), ha_innobase::delete_table():
Implement a fast path for temporary tables. We will no longer allow
temporary tables to use the adaptive hash index.
dict_table_t::mdl_name: The original table name for the purpose of
acquiring MDL in purge, to prevent a race condition between a
DDL transaction that is dropping a table, and purge processing
undo log records of DML that had executed before the DDL operation.
For #sql-backup- tables during ALTER TABLE...ALGORITHM=COPY, the
dict_table_t::mdl_name will differ from dict_table_t::name.
dict_table_t::parse_name(): Use mdl_name instead of name.
dict_table_rename_in_cache(): Update mdl_name.
For the internal FTS_ tables of FULLTEXT INDEX, purge would
acquire MDL on the FTS_ table name, but not on the main table,
and therefore it would be able to run concurrently with a
DDL transaction that is dropping the table. Previously, the
DROP TABLE queue hack prevented a race between purge and DDL.
For now, we introduce purge_sys.stop_FTS() to prevent purge from
opening any table, while a DDL transaction that may drop FTS_
tables is in progress. The function fts_lock_table(), which will
be invoked before the dictionary is locked, will wait for
purge to release any table handles.
trx_t::drop_table_statistics(): Drop statistics for the table.
This replaces dict_stats_drop_index(). We will drop or rename
persistent statistics atomically as part of DDL transactions.
On lock conflict for dropping statistics, we will fail instantly
with DB_LOCK_WAIT_TIMEOUT, because we will be holding the
exclusive data dictionary latch.
trx_t::commit_cleanup(): Separated from trx_t::commit_in_memory().
Relax an assertion around fts_commit() and allow DB_LOCK_WAIT_TIMEOUT
in addition to DB_DUPLICATE_KEY. The call to fts_commit() is
entirely misplaced here and may obviously break the consistency
of transactions that affect FULLTEXT INDEX. It needs to be fixed
separately.
dict_table_t::n_foreign_key_checks_running: Remove (MDEV-21175).
The counter was a work-around for missing meta-data locking (MDL)
on the SQL layer, and not really needed in MariaDB.
ER_TABLE_IN_FK_CHECK: Replaced with ER_UNUSED_28.
HA_ERR_TABLE_IN_FK_CHECK: Remove.
row_ins_check_foreign_constraints(): Do not acquire
dict_sys.latch either. The SQL-layer MDL will protect us.
This was reviewed by Thirunarayanan Balathandayuthapani
and tested by Matthias Leich.
2021-06-09 17:02:55 +03:00
|
|
|
--error ER_LOCK_WAIT_TIMEOUT
|
|
|
|
|
DROP TABLE t2;
|
|
|
|
|
XA ROLLBACK 'y';
|
|
|
|
|
DROP TABLE t2;
|
2024-05-21 09:52:35 +03:00
|
|
|
CREATE TABLE t3(a INT PRIMARY KEY REFERENCES t1(a)) ENGINE=InnoDB;
|
|
|
|
|
XA START 'a';
|
|
|
|
|
INSERT INTO t3 SET a=1;
|
|
|
|
|
--error ER_NO_REFERENCED_ROW_2
|
|
|
|
|
INSERT INTO t3 SET a=42;
|
|
|
|
|
XA END 'a';
|
|
|
|
|
XA PREPARE 'a';
|
2020-06-05 14:59:33 +03:00
|
|
|
|
|
|
|
|
SET GLOBAL innodb_fast_shutdown=0;
|
|
|
|
|
--source include/restart_mysqld.inc
|
|
|
|
|
|
2024-05-21 09:52:35 +03:00
|
|
|
XA COMMIT 'a';
|
|
|
|
|
SELECT * FROM t3;
|
|
|
|
|
DROP TABLE t3,t1;
|