mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
6bf6272fda
bug #57006 "Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK" and bug #54673 "It takes too long to get readlock for 'FLUSH TABLES WITH READ LOCK'". The first bug manifested itself as a deadlock which occurred when a connection, which had some table open through HANDLER statement, tried to update some data through DML statement while another connection tried to execute FLUSH TABLES WITH READ LOCK concurrently. What happened was that FTWRL in the second connection managed to perform first step of GRL acquisition and thus blocked all upcoming DML. After that it started to wait for table open through HANDLER statement to be flushed. When the first connection tried to execute DML it has started to wait for GRL/the second connection creating deadlock. The second bug manifested itself as starvation of FLUSH TABLES WITH READ LOCK statements in cases when there was a constant stream of concurrent DML statements (in two or more connections). This has happened because requests for protection against GRL which were acquired by DML statements were ignoring presence of pending GRL and thus the latter was starved. This patch solves both these problems by re-implementing GRL using metadata locks. Similar to the old implementation acquisition of GRL in new implementation is two-step. During the first step we block all concurrent DML and DDL statements by acquiring global S metadata lock (each DML and DDL statement acquires global IX lock for its duration). During the second step we block commits by acquiring global S lock in COMMIT namespace (commit code acquires global IX lock in this namespace). Note that unlike in old implementation acquisition of protection against GRL in DML and DDL is semi-automatic. We assume that any statement which should be blocked by GRL will either open and acquires write-lock on tables or acquires metadata locks on objects it is going to modify. For any such statement global IX metadata lock is automatically acquired for its duration. The first problem is solved because waits for GRL become visible to deadlock detector in metadata locking subsystem and thus deadlocks like one in the first bug become impossible. The second problem is solved because global S locks which are used for GRL implementation are given preference over IX locks which are acquired by concurrent DML (and we can switch to fair scheduling in future if needed). Important change: FTWRL/GRL no longer blocks DML and DDL on temporary tables. Before this patch behavior was not consistent in this respect: in some cases DML/DDL statements on temporary tables were blocked while in others they were not. Since the main use cases for FTWRL are various forms of backups and temporary tables are not preserved during backups we have opted for consistently allowing DML/DDL on temporary tables during FTWRL/GRL. Important change: This patch changes thread state names which are used when DML/DDL of FTWRL is waiting for global read lock. It is now either "Waiting for global read lock" or "Waiting for commit lock" depending on the stage on which FTWRL is. Incompatible change: To solve deadlock in events code which was exposed by this patch we have to replace LOCK_event_metadata mutex with metadata locks on events. As result we have to prohibit DDL on events under LOCK TABLES. This patch also adds extensive test coverage for interaction of DML/DDL and FTWRL. Performance of new and old global read lock implementations in sysbench tests were compared. There were no significant difference between new and old implementations. mysql-test/include/check_ftwrl_compatible.inc: Added helper script which allows to check that a statement is compatible with FLUSH TABLES WITH READ LOCK. mysql-test/include/check_ftwrl_incompatible.inc: Added helper script which allows to check that a statement is incompatible with FLUSH TABLES WITH READ LOCK. mysql-test/include/handler.inc: Adjusted test case to the fact that now DROP TABLE closes open HANDLERs for the table to be dropped before checking if there active FTWRL in this connection. mysql-test/include/wait_show_condition.inc: Fixed small error in the timeout message. The correct name of variable used as parameter for this script is "$condition" and not "$wait_condition". mysql-test/r/delayed.result: Added test coverage for scenario which triggered assert in metadata locking subsystem. mysql-test/r/events_2.result: Updated test results after prohibiting event DDL operations under LOCK TABLES. mysql-test/r/flush.result: Added test coverage for bug #57006 "Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK". mysql-test/r/flush_read_lock.result: Added test coverage for various aspects of FLUSH TABLES WITH READ LOCK functionality. mysql-test/r/flush_read_lock_kill.result: Adjusted test case after replacing custom global read lock implementation with one based on metadata locks. Use new debug_sync point. Do not disable concurrent inserts as now InnoDB we always use InnoDB table. mysql-test/r/handler_innodb.result: Adjusted test case to the fact that now DROP TABLE closes open HANDLERs for the table to be dropped before checking if there active FTWRL in this connection. mysql-test/r/handler_myisam.result: Adjusted test case to the fact that now DROP TABLE closes open HANDLERs for the table to be dropped before checking if there active FTWRL in this connection. mysql-test/r/mdl_sync.result: Adjusted test case after replacing custom global read lock implementation with one based on metadata locks. Replaced usage of GRL-specific debug_sync's with appropriate sync points in MDL subsystem. mysql-test/suite/perfschema/r/dml_setup_instruments.result: Updated test results after removing global COND_global_read_lock condition variable. mysql-test/suite/perfschema/r/func_file_io.result: Ensure that this test doesn't affect subsequent tests. At the end of its execution enable back P_S instrumentation which this test disables at some point. mysql-test/suite/perfschema/r/func_mutex.result: Ensure that this test doesn't affect subsequent tests. At the end of its execution enable back P_S instrumentation which this test disables at some point. mysql-test/suite/perfschema/r/global_read_lock.result: Adjusted test case to take into account that new GRL implementation is based on MDL. mysql-test/suite/perfschema/r/server_init.result: Adjusted test case after replacing custom global read lock implementation with one based on MDL and replacing LOCK_event_metadata mutex with metadata lock. mysql-test/suite/perfschema/t/func_file_io.test: Ensure that this test doesn't affect subsequent tests. At the end of its execution enable back P_S instrumentation which this test disables at some point. mysql-test/suite/perfschema/t/func_mutex.test: Ensure that this test doesn't affect subsequent tests. At the end of its execution enable back P_S instrumentation which this test disables at some point. mysql-test/suite/perfschema/t/global_read_lock.test: Adjusted test case to take into account that new GRL implementation is based on MDL. mysql-test/suite/perfschema/t/server_init.test: Adjusted test case after replacing custom global read lock implementation with one based on MDL and replacing LOCK_event_metadata mutex with metadata lock. mysql-test/suite/rpl/r/rpl_tmp_table_and_DDL.result: Updated test results after prohibiting event DDL under LOCK TABLES. mysql-test/t/delayed.test: Added test coverage for scenario which triggered assert in metadata locking subsystem. mysql-test/t/events_2.test: Updated test case after prohibiting event DDL operations under LOCK TABLES. mysql-test/t/flush.test: Added test coverage for bug #57006 "Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK". mysql-test/t/flush_block_commit.test: Adjusted test case after changing thread state name which is used when COMMIT waits for FLUSH TABLES WITH READ LOCK from "Waiting for release of readlock" to "Waiting for commit lock". mysql-test/t/flush_block_commit_notembedded.test: Adjusted test case after changing thread state name which is used when DML waits for FLUSH TABLES WITH READ LOCK. Now we use "Waiting for global read lock" in this case. mysql-test/t/flush_read_lock.test: Added test coverage for various aspects of FLUSH TABLES WITH READ LOCK functionality. mysql-test/t/flush_read_lock_kill-master.opt: We no longer need to use make_global_read_lock_block_commit_loop debug tag in this test. Instead we rely on an appropriate debug_sync point in MDL code. mysql-test/t/flush_read_lock_kill.test: Adjusted test case after replacing custom global read lock implementation with one based on metadata locks. Use new debug_sync point. Do not disable concurrent inserts as now InnoDB we always use InnoDB table. mysql-test/t/lock_multi.test: Adjusted test case after changing thread state names which are used when DML or DDL waits for FLUSH TABLES WITH READ LOCK to "Waiting for global read lock". mysql-test/t/mdl_sync.test: Adjusted test case after replacing custom global read lock implementation with one based on metadata locks. Replaced usage of GRL-specific debug_sync's with appropriate sync points in MDL subsystem. Updated thread state names which are used when DDL waits for FTWRL. mysql-test/t/trigger_notembedded.test: Adjusted test case after changing thread state names which are used when DML or DDL waits for FLUSH TABLES WITH READ LOCK to "Waiting for global read lock". sql/event_data_objects.cc: Removed Event_queue_element::status/last_executed_changed members and Event_queue_element::update_timing_fields() method. We no longer use this class for updating mysql.events once event is chosen for execution. Accesses to instances of this class in scheduler thread require protection by Event_queue::LOCK_event_queue mutex and we try to avoid updating table while holding this lock. sql/event_data_objects.h: Removed Event_queue_element::status/last_executed_changed members and Event_queue_element::update_timing_fields() method. We no longer use this class for updating mysql.events once event is chosen for execution. Accesses to instances of this class in scheduler thread require protection by Event_queue::LOCK_event_queue mutex and we try to avoid updating table while holding this lock. sql/event_db_repository.cc: - Changed Event_db_repository methods to not release all metadata locks once they are done updating mysql.events table. This allows to keep metadata lock protecting against GRL and lock protecting particular event around until corresponding DDL statement is written to the binary log. - Removed logic for conditional update of "status" and "last_executed" fields from update_timing_fields_for_event() method. In the only case when this method is called now "last_executed" is always modified and tracking change of "status" is too much hassle. sql/event_db_repository.h: Removed logic for conditional update of "status" and "last_executed" fields from Event_db_repository:: update_timing_fields_for_event() method. In the only case when this method is called now "last_executed" is always modified and tracking change of "status" field is too much hassle. sql/event_queue.cc: Changed event scheduler code not to update mysql.events table while holding Event_queue::LOCK_event_queue mutex. Doing so led to a deadlock with a new GRL implementation. This deadlock didn't occur with old implementation due to fact that code acquiring protection against GRL ignored pending GRL requests (which lead to GRL starvation). One of goals of new implementation is to disallow GRL starvation and so we have to solve problem with this deadlock in a different way. sql/events.cc: Changed methods of Events class to acquire protection against GRL while perfoming DDL statement and keep it until statement is written to the binary log. Unfortunately this step together with new GRL implementation exposed deadlock involving Events::LOCK_event_metadata and GRL. To solve it Events::LOCK_event_metadata mutex was replaced with a metadata lock on event. As a side-effect events DDL has to be prohibited under LOCK TABLES even in cases when mysql.events table was explicitly locked for write. sql/events.h: Replaced Events::LOCK_event_metadata mutex with a metadata lock on event. sql/ha_ndbcluster.cc: Updated code after replacing custom global read lock implementation with one based on MDL. Since MDL subsystem should now be able to detect deadlocks involving metadata locks and GRL there is no need for special handling of active GRL. sql/handler.cc: Replaced custom implementation of global read lock with one based on metadata locks. Consequently when doing commit instead of calling method of Global_read_lock class to acquire protection against GRL we simply acquire IX in COMMIT namespace. sql/lock.cc: Replaced custom implementation of global read lock with one based on metadata locks. This step allows to expose wait for GRL to deadlock detector of MDL subsystem and thus succesfully resolve deadlocks similar to one behind bug #57006 "Deadlock between HANDLER and FLUSH TABLES WITH READ LOCK". It also solves problem with GRL starvation described in bug #54673 "It takes too long to get readlock for 'FLUSH TABLES WITH READ LOCK'" since metadata locks used by GRL give preference to FTWRL statement instead of DML statements (if needed in future this can be changed to fair scheduling). Similar to old implementation of acquisition of GRL is two-step. During the first step we block all concurrent DML and DDL statements by acquiring global S metadata lock (each DML and DDL statement acquires global IX lock for its duration). During the second step we block commits by acquiring global S lock in COMMIT namespace (commit code acquires global IX lock in this namespace). Note that unlike in old implementation acquisition of protection against GRL in DML and DDL is semi-automatic. We assume that any statement which should be blocked by GRL will either open and acquires write-lock on tables or acquires metadata locks on objects it is going to modify. For any such statement global IX metadata lock is automatically acquired for its duration. To support this change: - Global_read_lock::lock/unlock_global_read_lock and make_global_read_lock_block_commit methods were changed accordingly. - Global_read_lock::wait_if_global_read_lock() and start_waiting_global_read_lock() methods were dropped. It is now responsibility of code acquiring metadata locks opening tables to acquire protection against GRL by explicitly taking global IX lock with statement duration. - Global variables, mutex and condition variable used by old implementation was removed. - lock_routine_name() was changed to use statement duration for its global IX lock. It was also renamed to lock_object_name() as it now also used to take metadata locks on events. - Global_read_lock::set_explicit_lock_duration() was added which allows not to release locks used for GRL when leaving prelocked mode. sql/lock.h: - Renamed lock_routine_name() to lock_object_name() and changed its signature to allow its usage for events. - Removed broadcast_refresh() function. It is no longer needed with new GRL implementation. sql/log_event.cc: Release metadata locks with statement duration at the end of processing legacy event for LOAD DATA. This ensures that replication thread processing such event properly releases its protection against global read lock. sql/mdl.cc: Changed MDL subsystem to support new MDL-based implementation of global read lock. Added COMMIT and EVENTS namespaces for metadata locks. Changed thread state name for GLOBAL namespace to "Waiting for global read lock". Optimized MDL_map::find_or_insert() method to avoid taking m_mutex mutex when looking up MDL_lock objects for GLOBAL or COMMIT namespaces. We keep pre-created MDL_lock objects for these namespaces around and simply return pointers to these global objects when needed. Changed MDL_lock/MDL_scoped_lock to properly handle notification of insert delayed handler threads when FTWRL takes global S lock. Introduced concept of lock duration. In addition to locks with transaction duration which work in the way which is similar to how locks worked before (i.e. they are released at the end of transaction), locks with statement and explicit duration were introduced. Locks with statement duration are automatically released at the end of statement. Locks with explicit duration require explicit release and obsolete concept of transactional sentinel. * Changed MDL_request and MDL_ticket classes to support notion of duration. * Changed MDL_context to keep locks with different duration in different lists. Changed code handling ticket list to take this into account. * Changed methods responsible for releasing locks to take into account duration of tickets. Particularly public MDL_context::release_lock() method now only can release tickets with explicit duration (there is still internal method which allows to specify duration). To release locks with statement or transaction duration one have to use release_statement/transactional_locks() methods. * Concept of savepoint for MDL subsystem now has to take into account locks with statement duration. Consequently MDL_savepoint class was introduced and methods working with savepoints were updated accordingly. * Added methods which allow to set duration for one or all locks in the context. sql/mdl.h: Changed MDL subsystem to support new MDL-based implementation of global read lock. Added COMMIT and EVENTS namespaces for metadata locks. Introduced concept of lock duration. In addition to locks with transaction duration which work in the way which is similar to how locks worked before (i.e. they are released at the end of transaction), locks with statement and explicit duration were introduced. Locks with statement duration are automatically released at the end of statement. Locks with explicit duration require explicit release and obsolete concept of transactional sentinel. * Changed MDL_request and MDL_ticket classes to support notion of duration. * Changed MDL_context to keep locks with different duration in different lists. Changed code handling ticket list to take this into account. * Changed methods responsible for releasing locks to take into account duration of tickets. Particularly public MDL_context::release_lock() method now only can release tickets with explicit duration (there is still internal method which allows to specify duration). To release locks with statement or transaction duration one have to use release_statement/transactional_locks() methods. * Concept of savepoint for MDL subsystem now has to take into account locks with statement duration. Consequently MDL_savepoint class was introduced and methods working with savepoints were updated accordingly. * Added methods which allow to set duration for one or all locks in the context. sql/mysqld.cc: Removed global mutex and condition variables which were used by old implementation of GRL. Also we no longer need to initialize Events::LOCK_event_metadata mutex as it was replaced with metadata locks on events. sql/mysqld.h: Removed global variable, mutex and condition variables which were used by old implementation of GRL. sql/rpl_rli.cc: When slave thread closes tables which were open for handling of RBR events ensure that it releases global IX lock which was acquired as protection against GRL. sql/sp.cc: Adjusted code to the new signature of lock_object/routine_name(), to the fact that one now needs specify duration of lock when initializing MDL_request and to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. sql/sp_head.cc: Ensure that statements in stored procedures release statement metadata locks and thus release their protectiong against GRL in proper moment in time. Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request. sql/sql_admin.cc: Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request. sql/sql_base.cc: - Implemented support for new approach to acquiring protection against global read lock. We no longer acquire such protection explicitly on the basis of statement flags. Instead we always rely on code which is responsible for acquiring metadata locks on object to be changed acquiring this protection. This is achieved by acquiring global IX metadata lock with statement duration. Code doing this also responsible for checking that current connection has no active GRL by calling an Global_read_lock::can_acquire_protection() method. Changed code in open_table() and lock_table_names() accordingly. Note that as result of this change DDL and DML on temporary tables is always compatible with GRL (before it was incompatible in some cases and compatible in other cases). - To speed-up code acquiring protection against GRL introduced m_has_protection_against_grl member in Open_table_context class. It indicates that protection was already acquired sometime during open_tables() execution and new attempts can be skipped. - Thanks to new GRL implementation calls to broadcast_refresh() became unnecessary and were removed. - Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request and to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. sql/sql_base.h: Adjusted code to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. Also introduced Open_table_context::m_has_protection_against_grl member which allows to avoid acquiring protection against GRL while opening tables if such protection was already acquired. sql/sql_class.cc: Changed THD::leave_locked_tables_mode() after transactional sentinel for metadata locks was obsoleted by introduction of locks with explicit duration. sql/sql_class.h: - Adjusted code to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. - Changed Global_read_lock class according to changes in global read lock implementation: * wait_if_global_read_lock and start_waiting_global_read_lock are now gone. Instead code needing protection against GRL has to acquire global IX metadata lock with statement duration itself. To help it new can_acquire_protection() was introduced. Also as result of the above change m_protection_count member is gone too. * Added m_mdl_blocks_commits_lock member to store metadata lock blocking commits. * Adjusted code to the fact that concept of transactional sentinel was obsoleted by concept of lock duration. - Removed CF_PROTECT_AGAINST_GRL flag as it is no longer necessary. New GRL implementation acquires protection against global read lock automagically when statement acquires metadata locks on tables or other objects it is going to change. sql/sql_db.cc: Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request. sql/sql_handler.cc: Removed call to broadcast_refresh() function. It is no longer needed with new GRL implementation. Adjusted code after introducing duration concept for metadata locks. Particularly to the fact transactional sentinel was replaced with explicit duration. sql/sql_handler.h: Renamed mysql_ha_move_tickets_after_trans_sentinel() to mysql_ha_set_explicit_lock_duration() after transactional sentinel was obsoleted by locks with explicit duration. sql/sql_insert.cc: Adjusted code handling delaying inserts after switching to new GRL implementation. Now connection thread initiating delayed insert has to acquire global IX lock in addition to metadata lock on table being inserted into. This IX lock protects against GRL and similarly to SW lock on table being inserted into has to be passed to handler thread in order to avoid deadlocks. sql/sql_lex.cc: LEX::protect_against_global_read_lock member is no longer necessary since protection against GRL is automatically taken by code acquiring metadata locks/opening tables. sql/sql_lex.h: LEX::protect_against_global_read_lock member is no longer necessary since protection against GRL is automatically taken by code acquiring metadata locks/opening tables. sql/sql_parse.cc: - Implemented support for new approach to acquiring protection against global read lock. We no longer acquire such protection explicitly on the basis of statement flags. Instead we always rely on code which is responsible for acquiring metadata locks on object to be changed acquiring this protection. This is achieved by acquiring global IX metadata lock with statement duration. This lock is automatically released at the end of statement execution. - Changed implementation of CREATE/DROP PROCEDURE/FUNCTION not to release metadata locks and thus protection against of GRL in the middle of statement execution. - Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request and to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. sql/sql_prepare.cc: Adjusted code to the to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. sql/sql_rename.cc: With new GRL implementation there is no need to explicitly acquire protection against GRL before renaming tables. This happens automatically in code which acquires metadata locks on tables being renamed. sql/sql_show.cc: Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request and to the fact that savepoints for MDL subsystem are now represented by MDL_savepoint class. sql/sql_table.cc: - With new GRL implementation there is no need to explicitly acquire protection against GRL before dropping tables. This happens automatically in code which acquires metadata locks on tables being dropped. - Changed mysql_alter_table() not to release lock on new table name explicitly and to rely on automatic release of locks at the end of statement instead. This was necessary since now MDL_context::release_lock() is supported only for locks for explicit duration. sql/sql_trigger.cc: With new GRL implementation there is no need to explicitly acquire protection against GRL before changing table triggers. This happens automatically in code which acquires metadata locks on tables which triggers are to be changed. sql/sql_update.cc: Fix bug exposed by GRL testing. During prepare phase acquire only S metadata locks instead of SW locks to keep prepare of multi-UPDATE compatible with concurrent LOCK TABLES WRITE and global read lock. sql/sql_view.cc: With new GRL implementation there is no need to explicitly acquire protection against GRL before creating view. This happens automatically in code which acquires metadata lock on view to be created. sql/sql_yacc.yy: LEX::protect_against_global_read_lock member is no longer necessary since protection against GRL is automatically taken by code acquiring metadata locks/opening tables. sql/table.cc: Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request. sql/table.h: Adjusted code to the fact that one now needs specify duration of lock when initializing MDL_request. sql/transaction.cc: Replaced custom implementation of global read lock with one based on metadata locks. Consequently when doing commit instead of calling method of Global_read_lock class to acquire protection against GRL we simply acquire IX in COMMIT namespace. Also adjusted code to the fact that MDL savepoint is now represented by MDL_savepoint class.
1861 lines
41 KiB
Text
1861 lines
41 KiB
Text
SET SESSION STORAGE_ENGINE = MyISAM;
|
|
drop table if exists t1,t3,t4,t5;
|
|
create table t1 (a int, b char(10), key a(a), key b(a,b));
|
|
insert into t1 values
|
|
(17,"ddd"),(18,"eee"),(19,"fff"),(19,"yyy"),
|
|
(14,"aaa"),(15,"bbb"),(16,"ccc"),(16,"xxx"),
|
|
(20,"ggg"),(21,"hhh"),(22,"iii");
|
|
handler t1 open as t2;
|
|
handler t2 read a=(SELECT 1);
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT 1)' at line 1
|
|
handler t2 read a first;
|
|
a b
|
|
14 aaa
|
|
handler t2 read a next;
|
|
a b
|
|
15 bbb
|
|
handler t2 read a next;
|
|
a b
|
|
16 ccc
|
|
handler t2 read a prev;
|
|
a b
|
|
15 bbb
|
|
handler t2 read a last;
|
|
a b
|
|
22 iii
|
|
handler t2 read a prev;
|
|
a b
|
|
21 hhh
|
|
handler t2 read a prev;
|
|
a b
|
|
20 ggg
|
|
handler t2 read a first;
|
|
a b
|
|
14 aaa
|
|
handler t2 read a prev;
|
|
a b
|
|
handler t2 read a last;
|
|
a b
|
|
22 iii
|
|
handler t2 read a prev;
|
|
a b
|
|
21 hhh
|
|
handler t2 read a next;
|
|
a b
|
|
22 iii
|
|
handler t2 read a next;
|
|
a b
|
|
handler t2 read a=(15);
|
|
a b
|
|
15 bbb
|
|
handler t2 read a=(16);
|
|
a b
|
|
16 ccc
|
|
handler t2 read a=(19,"fff");
|
|
ERROR 42000: Too many key parts specified; max 1 parts allowed
|
|
handler t2 read b=(19,"fff");
|
|
a b
|
|
19 fff
|
|
handler t2 read b=(19,"yyy");
|
|
a b
|
|
19 yyy
|
|
handler t2 read b=(19);
|
|
a b
|
|
19 fff
|
|
handler t1 read a last;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
handler t2 read a=(11);
|
|
a b
|
|
handler t2 read a>=(11);
|
|
a b
|
|
14 aaa
|
|
handler t2 read a=(18);
|
|
a b
|
|
18 eee
|
|
handler t2 read a>=(18);
|
|
a b
|
|
18 eee
|
|
handler t2 read a>(18);
|
|
a b
|
|
19 fff
|
|
handler t2 read a<=(18);
|
|
a b
|
|
18 eee
|
|
handler t2 read a<(18);
|
|
a b
|
|
17 ddd
|
|
handler t2 read a first limit 5;
|
|
a b
|
|
14 aaa
|
|
15 bbb
|
|
16 ccc
|
|
16 xxx
|
|
17 ddd
|
|
handler t2 read a next limit 3;
|
|
a b
|
|
18 eee
|
|
19 fff
|
|
19 yyy
|
|
handler t2 read a prev limit 10;
|
|
a b
|
|
19 fff
|
|
18 eee
|
|
17 ddd
|
|
16 xxx
|
|
16 ccc
|
|
15 bbb
|
|
14 aaa
|
|
handler t2 read a>=(16) limit 4;
|
|
a b
|
|
16 ccc
|
|
16 xxx
|
|
17 ddd
|
|
18 eee
|
|
handler t2 read a>=(16) limit 2,2;
|
|
a b
|
|
17 ddd
|
|
18 eee
|
|
handler t2 read a last limit 3;
|
|
a b
|
|
22 iii
|
|
21 hhh
|
|
20 ggg
|
|
handler t2 read a=(19);
|
|
a b
|
|
19 fff
|
|
handler t2 read a=(19) where b="yyy";
|
|
a b
|
|
19 yyy
|
|
handler t2 read first;
|
|
a b
|
|
17 ddd
|
|
handler t2 read next;
|
|
a b
|
|
18 eee
|
|
handler t2 read next;
|
|
a b
|
|
19 fff
|
|
handler t2 read last;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
|
|
handler t2 close;
|
|
handler t1 open;
|
|
handler t1 read a next;
|
|
a b
|
|
14 aaa
|
|
handler t1 read a next;
|
|
a b
|
|
15 bbb
|
|
handler t1 close;
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
a b
|
|
22 iii
|
|
handler t1 read a prev;
|
|
a b
|
|
21 hhh
|
|
handler t1 close;
|
|
handler t1 open as t2;
|
|
handler t2 read first;
|
|
a b
|
|
17 ddd
|
|
alter table t1 engine = MyISAM;
|
|
handler t2 read first;
|
|
ERROR 42S02: Unknown table 't2' in HANDLER
|
|
handler t1 open as t2;
|
|
drop table t1;
|
|
create table t1 (a int);
|
|
insert into t1 values (17);
|
|
handler t2 read first;
|
|
ERROR 42S02: Unknown table 't2' in HANDLER
|
|
handler t1 open as t2;
|
|
alter table t1 engine=MEMORY;
|
|
handler t2 read first;
|
|
ERROR 42S02: Unknown table 't2' in HANDLER
|
|
drop table t1;
|
|
create table t1 (a int);
|
|
insert into t1 values (1),(2),(3),(4),(5),(6);
|
|
delete from t1 limit 2;
|
|
handler t1 open;
|
|
handler t1 read first;
|
|
a
|
|
3
|
|
handler t1 read first limit 1,1;
|
|
a
|
|
4
|
|
handler t1 read first limit 2,2;
|
|
a
|
|
5
|
|
6
|
|
delete from t1 limit 3;
|
|
handler t1 read first;
|
|
a
|
|
6
|
|
drop table t1;
|
|
create table t1(a int, index(a));
|
|
insert into t1 values (1), (2), (3);
|
|
handler t1 open;
|
|
handler t1 read a=(W);
|
|
ERROR 42S22: Unknown column 'W' in 'field list'
|
|
handler t1 read a=(a);
|
|
ERROR HY000: Incorrect arguments to HANDLER ... READ
|
|
drop table t1;
|
|
create table t1 (a char(5));
|
|
insert into t1 values ("Ok");
|
|
handler t1 open as t;
|
|
handler t read first;
|
|
a
|
|
Ok
|
|
use mysql;
|
|
handler t read first;
|
|
a
|
|
Ok
|
|
handler t close;
|
|
handler test.t1 open as t;
|
|
handler t read first;
|
|
a
|
|
Ok
|
|
handler t close;
|
|
use test;
|
|
drop table t1;
|
|
create table t1 ( a int, b int, INDEX a (a) );
|
|
insert into t1 values (1,2), (2,1);
|
|
handler t1 open;
|
|
handler t1 read a=(1) where b=2;
|
|
a b
|
|
1 2
|
|
handler t1 read a=(1) where b=3;
|
|
a b
|
|
handler t1 read a=(1) where b=1;
|
|
a b
|
|
handler t1 close;
|
|
drop table t1;
|
|
drop database if exists test_test;
|
|
create database test_test;
|
|
use test_test;
|
|
create table t1(table_id char(20) primary key);
|
|
insert into t1 values ('test_test.t1');
|
|
insert into t1 values ('');
|
|
handler t1 open;
|
|
handler t1 read first limit 9;
|
|
table_id
|
|
test_test.t1
|
|
|
|
create table t2(table_id char(20) primary key);
|
|
insert into t2 values ('test_test.t2');
|
|
insert into t2 values ('');
|
|
handler t2 open;
|
|
handler t2 read first limit 9;
|
|
table_id
|
|
test_test.t2
|
|
|
|
use test;
|
|
drop table if exists t1;
|
|
create table t1(table_id char(20) primary key);
|
|
insert into t1 values ('test.t1');
|
|
insert into t1 values ('');
|
|
handler t1 open;
|
|
ERROR 42000: Not unique table/alias: 't1'
|
|
use test;
|
|
handler test.t1 read first limit 9;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'read first limit 9' at line 1
|
|
handler test_test.t1 read first limit 9;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'read first limit 9' at line 1
|
|
handler t1 read first limit 9;
|
|
table_id
|
|
test_test.t1
|
|
|
|
handler test_test.t2 read first limit 9;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'read first limit 9' at line 1
|
|
handler t2 read first limit 9;
|
|
table_id
|
|
test_test.t2
|
|
|
|
handler test_test.t1 close;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'close' at line 1
|
|
handler t1 close;
|
|
drop table test_test.t1;
|
|
handler test_test.t2 close;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'close' at line 1
|
|
handler t2 close;
|
|
drop table test_test.t2;
|
|
drop database test_test;
|
|
use test;
|
|
handler test.t1 close;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'close' at line 1
|
|
handler t1 close;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
drop table test.t1;
|
|
drop database if exists test_test;
|
|
drop table if exists t1;
|
|
drop table if exists t2;
|
|
drop table if exists t3;
|
|
create database test_test;
|
|
use test_test;
|
|
create table t1 (c1 char(20));
|
|
insert into t1 values ('test_test.t1');
|
|
create table t3 (c1 char(20));
|
|
insert into t3 values ('test_test.t3');
|
|
handler t1 open;
|
|
handler t1 read first limit 9;
|
|
c1
|
|
test_test.t1
|
|
handler t1 open h1;
|
|
handler h1 read first limit 9;
|
|
c1
|
|
test_test.t1
|
|
use test;
|
|
create table t1 (c1 char(20));
|
|
create table t2 (c1 char(20));
|
|
create table t3 (c1 char(20));
|
|
insert into t1 values ('t1');
|
|
insert into t2 values ('t2');
|
|
insert into t3 values ('t3');
|
|
handler t1 open;
|
|
ERROR 42000: Not unique table/alias: 't1'
|
|
handler t2 open t1;
|
|
ERROR 42000: Not unique table/alias: 't1'
|
|
handler t3 open t1;
|
|
ERROR 42000: Not unique table/alias: 't1'
|
|
handler t1 read first limit 9;
|
|
c1
|
|
test_test.t1
|
|
handler test.t1 close;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'close' at line 1
|
|
handler test.t1 open h1;
|
|
ERROR 42000: Not unique table/alias: 'h1'
|
|
handler test_test.t1 open h1;
|
|
ERROR 42000: Not unique table/alias: 'h1'
|
|
handler test_test.t3 open h3;
|
|
handler test.t1 open h2;
|
|
handler t1 read first limit 9;
|
|
c1
|
|
test_test.t1
|
|
handler h1 read first limit 9;
|
|
c1
|
|
test_test.t1
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t1
|
|
handler h3 read first limit 9;
|
|
c1
|
|
test_test.t3
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t1
|
|
handler test.h1 close;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'close' at line 1
|
|
handler t1 close;
|
|
handler h1 close;
|
|
handler h2 close;
|
|
handler t1 read first limit 9;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
handler h1 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1' in HANDLER
|
|
handler h2 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h2' in HANDLER
|
|
handler h3 read first limit 9;
|
|
c1
|
|
test_test.t3
|
|
handler h3 read first limit 9;
|
|
c1
|
|
test_test.t3
|
|
use test_test;
|
|
handler h3 read first limit 9;
|
|
c1
|
|
test_test.t3
|
|
handler test.h3 read first limit 9;
|
|
ERROR 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'read first limit 9' at line 1
|
|
handler h3 close;
|
|
use test;
|
|
drop table t3;
|
|
drop table t2;
|
|
drop table t1;
|
|
drop database test_test;
|
|
create table t1 (c1 char(20));
|
|
insert into t1 values ("t1");
|
|
handler t1 open as h1;
|
|
handler h1 read first limit 9;
|
|
c1
|
|
t1
|
|
create table t2 (c1 char(20));
|
|
insert into t2 values ("t2");
|
|
handler t2 open as h2;
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t2
|
|
create table t3 (c1 char(20));
|
|
insert into t3 values ("t3");
|
|
handler t3 open as h3;
|
|
handler h3 read first limit 9;
|
|
c1
|
|
t3
|
|
create table t4 (c1 char(20));
|
|
insert into t4 values ("t4");
|
|
handler t4 open as h4;
|
|
handler h4 read first limit 9;
|
|
c1
|
|
t4
|
|
create table t5 (c1 char(20));
|
|
insert into t5 values ("t5");
|
|
handler t5 open as h5;
|
|
handler h5 read first limit 9;
|
|
c1
|
|
t5
|
|
alter table t1 engine=MyISAM;
|
|
handler h1 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1' in HANDLER
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t2
|
|
handler h3 read first limit 9;
|
|
c1
|
|
t3
|
|
handler h4 read first limit 9;
|
|
c1
|
|
t4
|
|
handler h5 read first limit 9;
|
|
c1
|
|
t5
|
|
alter table t5 engine=MyISAM;
|
|
handler h1 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1' in HANDLER
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t2
|
|
handler h3 read first limit 9;
|
|
c1
|
|
t3
|
|
handler h4 read first limit 9;
|
|
c1
|
|
t4
|
|
handler h5 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h5' in HANDLER
|
|
alter table t3 engine=MyISAM;
|
|
handler h1 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1' in HANDLER
|
|
handler h2 read first limit 9;
|
|
c1
|
|
t2
|
|
handler h3 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h3' in HANDLER
|
|
handler h4 read first limit 9;
|
|
c1
|
|
t4
|
|
handler h5 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h5' in HANDLER
|
|
handler h2 close;
|
|
handler h4 close;
|
|
handler t1 open as h1_1;
|
|
handler t1 open as h1_2;
|
|
handler t1 open as h1_3;
|
|
handler h1_1 read first limit 9;
|
|
c1
|
|
t1
|
|
handler h1_2 read first limit 9;
|
|
c1
|
|
t1
|
|
handler h1_3 read first limit 9;
|
|
c1
|
|
t1
|
|
alter table t1 engine=MyISAM;
|
|
handler h1_1 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1_1' in HANDLER
|
|
handler h1_2 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1_2' in HANDLER
|
|
handler h1_3 read first limit 9;
|
|
ERROR 42S02: Unknown table 'h1_3' in HANDLER
|
|
drop table t1;
|
|
drop table t2;
|
|
drop table t3;
|
|
drop table t4;
|
|
drop table t5;
|
|
create table t1 (c1 int);
|
|
insert into t1 values (1);
|
|
handler t1 open;
|
|
handler t1 read first;
|
|
c1
|
|
1
|
|
send the below to another connection, do not wait for the result
|
|
optimize table t1;
|
|
proceed with the normal connection
|
|
handler t1 read next;
|
|
c1
|
|
1
|
|
handler t1 close;
|
|
read the result from the other connection
|
|
Table Op Msg_type Msg_text
|
|
test.t1 optimize status OK
|
|
proceed with the normal connection
|
|
drop table t1;
|
|
CREATE TABLE t1 ( no1 smallint(5) NOT NULL default '0', no2 int(10) NOT NULL default '0', PRIMARY KEY (no1,no2));
|
|
INSERT INTO t1 VALUES (1,274),(1,275),(2,6),(2,8),(4,1),(4,2);
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ `primary` = (1, 1000);
|
|
no1 no2
|
|
HANDLER t1 READ `primary` PREV;
|
|
no1 no2
|
|
1 275
|
|
DROP TABLE t1;
|
|
create table t1 (c1 int);
|
|
insert into t1 values (14397);
|
|
flush tables with read lock;
|
|
drop table t1;
|
|
ERROR HY000: Can't execute the query because you have a conflicting read lock
|
|
send the below to another connection, do not wait for the result
|
|
drop table t1;
|
|
proceed with the normal connection
|
|
select * from t1;
|
|
c1
|
|
14397
|
|
unlock tables;
|
|
read the result from the other connection
|
|
proceed with the normal connection
|
|
select * from t1;
|
|
ERROR 42S02: Table 'test.t1' doesn't exist
|
|
drop table if exists t1;
|
|
Warnings:
|
|
Note 1051 Unknown table 't1'
|
|
drop table if exists t1;
|
|
create table t1 (a int) ENGINE=MEMORY;
|
|
--> client 2
|
|
handler t1 open;
|
|
ERROR HY000: Table storage engine for 't1' doesn't have this option
|
|
--> client 1
|
|
drop table t1;
|
|
drop table if exists t1;
|
|
create table t1 (a int);
|
|
handler t1 open as t1_alias;
|
|
handler t1_alias read a next;
|
|
ERROR 42000: Key 'a' doesn't exist in table 't1_alias'
|
|
handler t1_alias READ a next where inexistent > 0;
|
|
ERROR 42S22: Unknown column 'inexistent' in 'field list'
|
|
handler t1_alias read a next;
|
|
ERROR 42000: Key 'a' doesn't exist in table 't1_alias'
|
|
handler t1_alias READ a next where inexistent > 0;
|
|
ERROR 42S22: Unknown column 'inexistent' in 'field list'
|
|
handler t1_alias close;
|
|
drop table t1;
|
|
drop table if exists t1,t2;
|
|
create table t1 (c1 int);
|
|
create table t2 (c1 int);
|
|
insert into t1 values (1);
|
|
insert into t2 values (2);
|
|
connection: default
|
|
handler t1 open;
|
|
handler t1 read first;
|
|
c1
|
|
1
|
|
connection: flush
|
|
flush tables;;
|
|
connection: waiter
|
|
connection: default
|
|
handler t2 open;
|
|
handler t2 read first;
|
|
c1
|
|
2
|
|
handler t1 read next;
|
|
c1
|
|
1
|
|
handler t1 close;
|
|
handler t2 close;
|
|
drop table t1,t2;
|
|
drop table if exists t1, t0;
|
|
create table t1 (c1 int);
|
|
connection: default
|
|
handler t1 open;
|
|
handler t1 read first;
|
|
c1
|
|
connection: flush
|
|
rename table t1 to t0;;
|
|
connection: waiter
|
|
connection: default
|
|
#
|
|
# RENAME placed two pending locks and waits.
|
|
# When HANDLER t0 OPEN does open_tables(), it calls
|
|
# mysql_ha_flush(), which in turn closes the open HANDLER for t1.
|
|
# RENAME TABLE gets unblocked. If it gets scheduled quickly
|
|
# and manages to complete before open_tables()
|
|
# of HANDLER t0 OPEN, open_tables() and therefore the whole
|
|
# HANDLER t0 OPEN succeeds. Otherwise open_tables()
|
|
# notices a pending or active exclusive metadata lock on t2
|
|
# and the whole HANDLER t0 OPEN fails with ER_LOCK_DEADLOCK
|
|
# error.
|
|
#
|
|
handler t0 open;
|
|
handler t0 close;
|
|
connection: flush
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
handler t1 close;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
drop table t0;
|
|
drop table if exists t1;
|
|
create temporary table t1 (a int, b char(1), key a(a), key b(a,b));
|
|
insert into t1 values (0,"a"),(1,"b"),(2,"c"),(3,"d"),(4,"e"),
|
|
(5,"f"),(6,"g"),(7,"h"),(8,"i"),(9,"j");
|
|
select a,b from t1;
|
|
a b
|
|
0 a
|
|
1 b
|
|
2 c
|
|
3 d
|
|
4 e
|
|
5 f
|
|
6 g
|
|
7 h
|
|
8 i
|
|
9 j
|
|
handler t1 open as a1;
|
|
handler a1 read a first;
|
|
a b
|
|
0 a
|
|
handler a1 read a next;
|
|
a b
|
|
1 b
|
|
handler a1 read a next;
|
|
a b
|
|
2 c
|
|
select a,b from t1;
|
|
ERROR HY000: Can't reopen table: 'a1'
|
|
handler a1 read a prev;
|
|
a b
|
|
1 b
|
|
handler a1 read a prev;
|
|
a b
|
|
0 a
|
|
handler a1 read a=(6) where b="g";
|
|
a b
|
|
6 g
|
|
handler a1 close;
|
|
select a,b from t1;
|
|
a b
|
|
0 a
|
|
1 b
|
|
2 c
|
|
3 d
|
|
4 e
|
|
5 f
|
|
6 g
|
|
7 h
|
|
8 i
|
|
9 j
|
|
handler t1 open as a2;
|
|
handler a2 read a first;
|
|
a b
|
|
0 a
|
|
handler a2 read a last;
|
|
a b
|
|
9 j
|
|
handler a2 read a prev;
|
|
a b
|
|
8 i
|
|
handler a2 close;
|
|
drop table t1;
|
|
drop table if exists t1,t2;
|
|
create table t1 (a int);
|
|
handler t1 open as t1_alias;
|
|
drop table t1;
|
|
create table t1 (a int);
|
|
handler t1 open as t1_alias;
|
|
flush tables;
|
|
drop table t1;
|
|
create table t1 (a int);
|
|
handler t1 open as t1_alias;
|
|
handler t1_alias close;
|
|
drop table t1;
|
|
create table t1 (a int);
|
|
handler t1 open as t1_alias;
|
|
handler t1_alias read first;
|
|
a
|
|
drop table t1;
|
|
handler t1_alias read next;
|
|
ERROR 42S02: Unknown table 't1_alias' in HANDLER
|
|
create table t1 (a int);
|
|
create temporary table t2 (a int, key(a));
|
|
handler t1 open as a1;
|
|
handler t2 open as a2;
|
|
handler a2 read a first;
|
|
a
|
|
drop table t1, t2;
|
|
handler a2 read a next;
|
|
ERROR 42S02: Unknown table 'a2' in HANDLER
|
|
handler a1 close;
|
|
ERROR 42S02: Unknown table 'a1' in HANDLER
|
|
create table t1 (a int, key(a));
|
|
create table t2 like t1;
|
|
handler t1 open as a1;
|
|
handler t2 open as a2;
|
|
handler a1 read a first;
|
|
a
|
|
handler a2 read a first;
|
|
a
|
|
alter table t1 add b int;
|
|
handler a1 close;
|
|
ERROR 42S02: Unknown table 'a1' in HANDLER
|
|
handler a2 close;
|
|
drop table t1, t2;
|
|
create table t1 (a int, key(a));
|
|
handler t1 open as a1;
|
|
handler a1 read a first;
|
|
a
|
|
rename table t1 to t2;
|
|
handler a1 read a first;
|
|
ERROR 42S02: Unknown table 'a1' in HANDLER
|
|
drop table t2;
|
|
create table t1 (a int, key(a));
|
|
create table t2 like t1;
|
|
handler t1 open as a1;
|
|
handler t2 open as a2;
|
|
handler a1 read a first;
|
|
a
|
|
handler a2 read a first;
|
|
a
|
|
optimize table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 optimize status Table is already up to date
|
|
handler a1 close;
|
|
ERROR 42S02: Unknown table 'a1' in HANDLER
|
|
handler a2 close;
|
|
drop table t1, t2;
|
|
create table t1 (a int, b char(1), key a(a), key b(a,b));
|
|
insert into t1 values (0,"a"),(1,"b"),(2,"c"),(3,"d"),(4,"e"),
|
|
(5,"f"),(6,"g"),(7,"h"),(8,"i"),(9,"j");
|
|
handler t1 open;
|
|
handler t1 read a first;
|
|
a b
|
|
0 a
|
|
handler t1 read a next;
|
|
a b
|
|
1 b
|
|
flush tables;
|
|
handler t1 read a next;
|
|
a b
|
|
0 a
|
|
handler t1 read a next;
|
|
a b
|
|
1 b
|
|
flush tables with read lock;
|
|
handler t1 read a next;
|
|
a b
|
|
0 a
|
|
unlock tables;
|
|
drop table t1;
|
|
handler t1 read a next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
drop table if exists t1;
|
|
# First test case which is supposed trigger the execution
|
|
# path on which problem was discovered.
|
|
create table t1 (a int);
|
|
insert into t1 values (1);
|
|
handler t1 open;
|
|
lock table t1 write;
|
|
alter table t1 engine=memory;
|
|
handler t1 read a next;
|
|
ERROR HY000: Table storage engine for 't1' doesn't have this option
|
|
handler t1 close;
|
|
unlock tables;
|
|
drop table t1;
|
|
# Now test case which was reported originally but which no longer
|
|
# triggers execution path which has caused the problem.
|
|
create table t1 (a int, key(a));
|
|
insert into t1 values (1);
|
|
handler t1 open;
|
|
alter table t1 engine=memory;
|
|
# Since S metadata lock was already acquired at HANDLER OPEN time
|
|
# and TL_READ lock requested by HANDLER READ is compatible with
|
|
# ALTER's TL_WRITE_ALLOW_READ the below statement should succeed
|
|
# without waiting. The old version of table should be used in it.
|
|
handler t1 read a next;
|
|
a
|
|
1
|
|
handler t1 close;
|
|
drop table t1;
|
|
USE information_schema;
|
|
HANDLER COLUMNS OPEN;
|
|
ERROR HY000: Incorrect usage of HANDLER OPEN and information_schema
|
|
USE test;
|
|
#
|
|
# Add test coverage for HANDLER and LOCK TABLES, HANDLER and DDL.
|
|
#
|
|
drop table if exists t1, t2, t3;
|
|
create table t1 (a int, key a (a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
create table t2 (a int, key a (a)) select * from t1;
|
|
create temporary table t3 (a int, key a (a)) select * from t2;
|
|
handler t1 open;
|
|
handler t2 open;
|
|
handler t3 open;
|
|
#
|
|
# No HANDLER sql is allowed under LOCK TABLES.
|
|
# But it does not implicitly closes all handlers.
|
|
#
|
|
lock table t1 read;
|
|
handler t1 open;
|
|
ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction
|
|
handler t1 read next;
|
|
ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction
|
|
handler t2 close;
|
|
ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction
|
|
handler t3 open;
|
|
ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction
|
|
# After UNLOCK TABLES handlers should be around and
|
|
# we should be able to continue reading through them.
|
|
unlock tables;
|
|
handler t1 read next;
|
|
a
|
|
1
|
|
handler t1 close;
|
|
handler t2 read next;
|
|
a
|
|
1
|
|
handler t2 close;
|
|
handler t3 read next;
|
|
a
|
|
1
|
|
handler t3 close;
|
|
drop temporary table t3;
|
|
#
|
|
# Other operations that implicitly close handler:
|
|
#
|
|
# TRUNCATE
|
|
#
|
|
handler t1 open;
|
|
truncate table t1;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
handler t1 open;
|
|
#
|
|
# CREATE TRIGGER
|
|
#
|
|
create trigger t1_ai after insert on t1 for each row set @a=1;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# DROP TRIGGER
|
|
#
|
|
handler t1 open;
|
|
drop trigger t1_ai;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# ALTER TABLE
|
|
#
|
|
handler t1 open;
|
|
alter table t1 add column b int;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# ANALYZE TABLE
|
|
#
|
|
handler t1 open;
|
|
analyze table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 analyze status Table is already up to date
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# OPTIMIZE TABLE
|
|
#
|
|
handler t1 open;
|
|
optimize table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 optimize status OK
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# REPAIR TABLE
|
|
#
|
|
handler t1 open;
|
|
repair table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 repair status OK
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# DROP TABLE, naturally.
|
|
#
|
|
handler t1 open;
|
|
drop table t1;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
create table t1 (a int, b int, key a (a)) select a from t2;
|
|
#
|
|
# RENAME TABLE, naturally
|
|
#
|
|
handler t1 open;
|
|
rename table t1 to t3;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# CREATE TABLE (even with IF NOT EXISTS clause,
|
|
# and the table exists).
|
|
#
|
|
handler t2 open;
|
|
create table if not exists t2 (a int);
|
|
Warnings:
|
|
Note 1050 Table 't2' already exists
|
|
handler t2 read next;
|
|
ERROR 42S02: Unknown table 't2' in HANDLER
|
|
rename table t3 to t1;
|
|
drop table t2;
|
|
#
|
|
# FLUSH TABLE doesn't close the table but loses the position
|
|
#
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
b a
|
|
NULL 5
|
|
flush table t1;
|
|
handler t1 read a prev;
|
|
b a
|
|
NULL 5
|
|
handler t1 close;
|
|
#
|
|
# FLUSH TABLES WITH READ LOCK behaves like FLUSH TABLE.
|
|
#
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
b a
|
|
NULL 5
|
|
flush tables with read lock;
|
|
handler t1 read a prev;
|
|
b a
|
|
NULL 5
|
|
handler t1 close;
|
|
unlock tables;
|
|
#
|
|
# Let us also check that these operations behave in similar
|
|
# way under LOCK TABLES.
|
|
#
|
|
# TRUNCATE under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
truncate table t1;
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
handler t1 open;
|
|
#
|
|
# CREATE TRIGGER under LOCK TABLES.
|
|
#
|
|
lock tables t1 write;
|
|
create trigger t1_ai after insert on t1 for each row set @a=1;
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# DROP TRIGGER under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
drop trigger t1_ai;
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# ALTER TABLE under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
alter table t1 drop column b;
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# ANALYZE TABLE under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
analyze table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 analyze status Table is already up to date
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# OPTIMIZE TABLE under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
optimize table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 optimize status OK
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# REPAIR TABLE under LOCK TABLES.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
repair table t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 repair status OK
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
#
|
|
# DROP TABLE under LOCK TABLES, naturally.
|
|
#
|
|
handler t1 open;
|
|
lock tables t1 write;
|
|
drop table t1;
|
|
unlock tables;
|
|
handler t1 read next;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
create table t1 (a int, b int, key a (a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
#
|
|
# FLUSH TABLE doesn't close the table but loses the position
|
|
#
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
a b
|
|
5 NULL
|
|
lock tables t1 write;
|
|
flush table t1;
|
|
unlock tables;
|
|
handler t1 read a prev;
|
|
a b
|
|
5 NULL
|
|
handler t1 close;
|
|
#
|
|
# Explore the effect of HANDLER locks on concurrent DDL
|
|
#
|
|
handler t1 open;
|
|
# Establishing auxiliary connections con1, con2, con3
|
|
# --> connection con1;
|
|
# Sending:
|
|
drop table t1 ;
|
|
# We can't use connection 'default' as wait_condition will
|
|
# autoclose handlers.
|
|
# --> connection con2
|
|
# Waitng for 'drop table t1' to get blocked...
|
|
# --> connection default
|
|
handler t1 read a prev;
|
|
a b
|
|
5 NULL
|
|
handler t1 read a prev;
|
|
a b
|
|
4 NULL
|
|
handler t1 close;
|
|
# --> connection con1
|
|
# Reaping 'drop table t1'...
|
|
# --> connection default
|
|
#
|
|
# Explore the effect of HANDLER locks in parallel with SELECT
|
|
#
|
|
create table t1 (a int, key a (a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
begin;
|
|
select * from t1;
|
|
a
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
a
|
|
5
|
|
handler t1 read a prev;
|
|
a
|
|
4
|
|
handler t1 close;
|
|
# --> connection con1;
|
|
# Sending:
|
|
drop table t1 ;
|
|
# --> connection con2
|
|
# Waiting for 'drop table t1' to get blocked...
|
|
# --> connection default
|
|
# We can still use the table, it's part of the transaction
|
|
select * from t1;
|
|
a
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
# Such are the circumstances that t1 is a part of transaction,
|
|
# thus we can reopen it in the handler
|
|
handler t1 open;
|
|
# We can commit the transaction, it doesn't close the handler
|
|
# and doesn't let DROP to proceed.
|
|
commit;
|
|
handler t1 read a prev;
|
|
a
|
|
5
|
|
handler t1 read a prev;
|
|
a
|
|
4
|
|
handler t1 read a prev;
|
|
a
|
|
3
|
|
handler t1 close;
|
|
# --> connection con1
|
|
# Now drop can proceed
|
|
# Reaping 'drop table t1'...
|
|
# --> connection default
|
|
#
|
|
# Demonstrate that HANDLER locks and transaction locks
|
|
# reside in the same context, and we don't back-off
|
|
# when have transaction or handler locks.
|
|
#
|
|
create table t1 (a int, key a (a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
create table t0 (a int, key a (a));
|
|
insert into t0 (a) values (1), (2), (3), (4), (5);
|
|
begin;
|
|
select * from t1;
|
|
a
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
# --> connection con2
|
|
# Sending:
|
|
rename table t0 to t3, t1 to t0, t3 to t1;
|
|
# --> connection con1
|
|
# Waiting for 'rename table ...' to get blocked...
|
|
# --> connection default
|
|
handler t0 open;
|
|
ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
|
|
select * from t0;
|
|
ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
|
|
handler t1 open;
|
|
commit;
|
|
handler t1 close;
|
|
# --> connection con2
|
|
# Reaping 'rename table ...'...
|
|
# --> connection default
|
|
handler t1 open;
|
|
handler t1 read a prev;
|
|
a
|
|
5
|
|
handler t1 close;
|
|
drop table t0;
|
|
#
|
|
# Originally there was a deadlock error in this test.
|
|
# With implementation of deadlock detector
|
|
# we no longer deadlock, but block and wait on a lock.
|
|
# The HANDLER is auto-closed as soon as the connection
|
|
# sees a pending conflicting lock against it.
|
|
#
|
|
create table t2 (a int, key a (a));
|
|
handler t1 open;
|
|
# --> connection con1
|
|
lock tables t2 read;
|
|
# --> connection con2
|
|
# Sending 'drop table t2'...
|
|
drop table t2;
|
|
# --> connection con1
|
|
# Waiting for 'drop table t2' to get blocked...
|
|
# --> connection default
|
|
# Sending 'select * from t2'
|
|
select * from t2;
|
|
# --> connection con1
|
|
# Waiting for 'select * from t2' to get blocked...
|
|
unlock tables;
|
|
# --> connection con2
|
|
# Reaping 'drop table t2'...
|
|
# --> connection default
|
|
# Reaping 'select * from t2'
|
|
ERROR 42S02: Table 'test.t2' doesn't exist
|
|
handler t1 close;
|
|
#
|
|
# ROLLBACK TO SAVEPOINT releases transactional locks,
|
|
# but has no effect on open HANDLERs
|
|
#
|
|
create table t2 like t1;
|
|
create table t3 like t1;
|
|
begin;
|
|
# Have something before the savepoint
|
|
select * from t3;
|
|
a
|
|
savepoint sv;
|
|
handler t1 open;
|
|
handler t1 read a first;
|
|
a
|
|
1
|
|
handler t1 read a next;
|
|
a
|
|
2
|
|
select * from t2;
|
|
a
|
|
# --> connection con1
|
|
# Sending:
|
|
drop table t1;
|
|
# --> connection con2
|
|
# Sending:
|
|
drop table t2;
|
|
# --> connection default
|
|
# Let DROP TABLE statements sync in. We must use
|
|
# a separate connection for that, because otherwise SELECT
|
|
# will auto-close the HANDLERs, becaues there are pending
|
|
# exclusive locks against them.
|
|
# --> connection con3
|
|
# Waiting for 'drop table t1' to get blocked...
|
|
# Waiting for 'drop table t2' to get blocked...
|
|
# Demonstrate that t2 lock was released and t2 was dropped
|
|
# after ROLLBACK TO SAVEPOINT
|
|
# --> connection default
|
|
rollback to savepoint sv;
|
|
# --> connection con2
|
|
# Reaping 'drop table t2'...
|
|
# Demonstrate that ROLLBACK TO SAVEPOINT didn't release the handler
|
|
# lock.
|
|
# --> connection default
|
|
handler t1 read a next;
|
|
a
|
|
3
|
|
handler t1 read a next;
|
|
a
|
|
4
|
|
# Demonstrate that the drop will go through as soon as we close the
|
|
# HANDLER
|
|
handler t1 close;
|
|
# connection con1
|
|
# Reaping 'drop table t1'...
|
|
# --> connection default
|
|
commit;
|
|
drop table t3;
|
|
#
|
|
# A few special cases when using SAVEPOINT/ROLLBACK TO
|
|
# SAVEPOINT and HANDLER.
|
|
#
|
|
# Show that rollback to the savepoint taken in the beginning
|
|
# of the transaction doesn't release mdl lock on
|
|
# the HANDLER that was opened later.
|
|
#
|
|
create table t1 (a int, key a(a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
create table t2 like t1;
|
|
begin;
|
|
savepoint sv;
|
|
handler t1 open;
|
|
handler t1 read a first;
|
|
a
|
|
1
|
|
handler t1 read a next;
|
|
a
|
|
2
|
|
select * from t2;
|
|
a
|
|
# --> connection con1
|
|
# Sending:
|
|
drop table t1;
|
|
# --> connection con2
|
|
# Sending:
|
|
drop table t2;
|
|
# --> connection default
|
|
# Let DROP TABLE statements sync in. We must use
|
|
# a separate connection for that, because otherwise SELECT
|
|
# will auto-close the HANDLERs, becaues there are pending
|
|
# exclusive locks against them.
|
|
# --> connection con3
|
|
# Waiting for 'drop table t1' to get blocked...
|
|
# Waiting for 'drop table t2' to get blocked...
|
|
# Demonstrate that t2 lock was released and t2 was dropped
|
|
# after ROLLBACK TO SAVEPOINT
|
|
# --> connection default
|
|
rollback to savepoint sv;
|
|
# --> connection con2
|
|
# Reaping 'drop table t2'...
|
|
# Demonstrate that ROLLBACK TO SAVEPOINT didn't release the handler
|
|
# lock.
|
|
# --> connection default
|
|
handler t1 read a next;
|
|
a
|
|
3
|
|
handler t1 read a next;
|
|
a
|
|
4
|
|
# Demonstrate that the drop will go through as soon as we close the
|
|
# HANDLER
|
|
handler t1 close;
|
|
# connection con1
|
|
# Reaping 'drop table t1'...
|
|
# --> connection default
|
|
commit;
|
|
#
|
|
# Show that rollback to the savepoint taken in the beginning
|
|
# of the transaction works properly (no valgrind warnins, etc),
|
|
# even though it's done after the HANDLER mdl lock that was there
|
|
# at the beginning is released and added again.
|
|
#
|
|
create table t1 (a int, key a(a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
create table t2 like t1;
|
|
create table t3 like t1;
|
|
insert into t3 (a) select a from t1;
|
|
begin;
|
|
handler t1 open;
|
|
savepoint sv;
|
|
handler t1 read a first;
|
|
a
|
|
1
|
|
select * from t2;
|
|
a
|
|
handler t1 close;
|
|
handler t3 open;
|
|
handler t3 read a first;
|
|
a
|
|
1
|
|
rollback to savepoint sv;
|
|
# --> connection con1
|
|
drop table t1, t2;
|
|
# Sending:
|
|
drop table t3;
|
|
# Let DROP TABLE statement sync in.
|
|
# --> connection con2
|
|
# Waiting for 'drop table t3' to get blocked...
|
|
# Demonstrate that ROLLBACK TO SAVEPOINT didn't release the handler
|
|
# lock.
|
|
# --> connection default
|
|
handler t3 read a next;
|
|
a
|
|
2
|
|
# Demonstrate that the drop will go through as soon as we close the
|
|
# HANDLER
|
|
handler t3 close;
|
|
# connection con1
|
|
# Reaping 'drop table t3'...
|
|
# --> connection default
|
|
commit;
|
|
#
|
|
# If we have to wait on an exclusive locks while having
|
|
# an open HANDLER, ER_LOCK_DEADLOCK is reported.
|
|
#
|
|
create table t1 (a int, key a(a));
|
|
create table t2 like t1;
|
|
handler t1 open;
|
|
# --> connection con1
|
|
lock table t1 write, t2 write;
|
|
# --> connection default
|
|
drop table t2;
|
|
# --> connection con2
|
|
# Waiting for 'drop table t2' to get blocked...
|
|
# --> connection con1
|
|
drop table t1;
|
|
ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
|
|
unlock tables;
|
|
# --> connection default
|
|
# Demonstrate that there is no deadlock with FLUSH TABLE,
|
|
# even though it is waiting for the other table to go away
|
|
create table t2 like t1;
|
|
# Sending:
|
|
flush table t2;
|
|
# --> connection con2
|
|
drop table t1;
|
|
# --> connection con1
|
|
unlock tables;
|
|
# --> connection default
|
|
# Reaping 'flush table t2'...
|
|
drop table t2;
|
|
#
|
|
# Bug #46224 HANDLER statements within a transaction might
|
|
# lead to deadlocks
|
|
#
|
|
create table t1 (a int, key a(a));
|
|
insert into t1 values (1), (2);
|
|
# --> connection default
|
|
begin;
|
|
select * from t1;
|
|
a
|
|
1
|
|
2
|
|
handler t1 open;
|
|
# --> connection con1
|
|
# Sending:
|
|
lock tables t1 write;
|
|
# --> connection con2
|
|
# Check that 'lock tables t1 write' waits until transaction which
|
|
# has read from the table commits.
|
|
# --> connection default
|
|
# The below 'handler t1 read ...' should not be blocked as
|
|
# 'lock tables t1 write' has not succeeded yet.
|
|
handler t1 read a next;
|
|
a
|
|
1
|
|
# Unblock 'lock tables t1 write'.
|
|
commit;
|
|
# --> connection con1
|
|
# Reap 'lock tables t1 write'.
|
|
# --> connection default
|
|
# Sending:
|
|
handler t1 read a next;
|
|
# --> connection con1
|
|
# Waiting for 'handler t1 read a next' to get blocked...
|
|
# The below 'drop table t1' should be able to proceed without
|
|
# waiting as it will force HANDLER to be closed.
|
|
drop table t1;
|
|
unlock tables;
|
|
# --> connection default
|
|
# Reaping 'handler t1 read a next'...
|
|
ERROR 42S02: Table 'test.t1' doesn't exist
|
|
handler t1 close;
|
|
# --> connection con1
|
|
# --> connection con2
|
|
# --> connection con3
|
|
#
|
|
# A temporary table test.
|
|
# Check that we don't loose positions of HANDLER opened
|
|
# against a temporary table.
|
|
#
|
|
create table t1 (a int, b int, key a (a));
|
|
insert into t1 (a) values (1), (2), (3), (4), (5);
|
|
create temporary table t2 (a int, b int, key a (a));
|
|
insert into t2 (a) select a from t1;
|
|
handler t1 open;
|
|
handler t1 read a next;
|
|
a b
|
|
1 NULL
|
|
handler t2 open;
|
|
handler t2 read a next;
|
|
a b
|
|
1 NULL
|
|
flush table t1;
|
|
handler t2 read a next;
|
|
a b
|
|
2 NULL
|
|
# Sic: the position is lost
|
|
handler t1 read a next;
|
|
a b
|
|
1 NULL
|
|
select * from t1;
|
|
a b
|
|
1 NULL
|
|
2 NULL
|
|
3 NULL
|
|
4 NULL
|
|
5 NULL
|
|
# Sic: the position is not lost
|
|
handler t2 read a next;
|
|
a b
|
|
3 NULL
|
|
select * from t2;
|
|
ERROR HY000: Can't reopen table: 't2'
|
|
handler t2 read a next;
|
|
a b
|
|
4 NULL
|
|
drop table t1;
|
|
drop temporary table t2;
|
|
#
|
|
# A test for lock_table_names()/unlock_table_names() function.
|
|
# It should work properly in presence of open HANDLER.
|
|
#
|
|
create table t1 (a int, b int, key a (a));
|
|
create table t2 like t1;
|
|
create table t3 like t1;
|
|
create table t4 like t1;
|
|
handler t1 open;
|
|
handler t2 open;
|
|
rename table t4 to t5, t3 to t4, t5 to t3;
|
|
handler t1 read first;
|
|
a b
|
|
handler t2 read first;
|
|
a b
|
|
drop table t1, t2, t3, t4;
|
|
#
|
|
# A test for FLUSH TABLES WITH READ LOCK and HANDLER statements.
|
|
#
|
|
set autocommit=0;
|
|
create table t1 (a int, b int, key a (a));
|
|
insert into t1 (a, b) values (1, 1), (2, 1), (3, 2), (4, 2), (5, 5);
|
|
create table t2 like t1;
|
|
insert into t2 (a, b) select a, b from t1;
|
|
create table t3 like t1;
|
|
insert into t3 (a, b) select a, b from t1;
|
|
commit;
|
|
flush tables with read lock;
|
|
handler t1 open;
|
|
lock table t1 read;
|
|
handler t1 read next;
|
|
ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction
|
|
# This implicitly leaves LOCK TABLES but doesn't drop the GLR
|
|
lock table not_exists_write read;
|
|
ERROR 42S02: Table 'test.not_exists_write' doesn't exist
|
|
# We still have the read lock.
|
|
drop table t1;
|
|
ERROR HY000: Can't execute the query because you have a conflicting read lock
|
|
handler t1 open;
|
|
select a from t2;
|
|
a
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
handler t1 read next;
|
|
a b
|
|
1 1
|
|
flush tables with read lock;
|
|
handler t2 open;
|
|
flush tables with read lock;
|
|
handler t1 read next;
|
|
a b
|
|
1 1
|
|
select a from t3;
|
|
a
|
|
1
|
|
2
|
|
3
|
|
4
|
|
5
|
|
handler t2 read next;
|
|
a b
|
|
1 1
|
|
handler t1 close;
|
|
rollback;
|
|
handler t2 close;
|
|
drop table t1;
|
|
ERROR HY000: Can't execute the query because you have a conflicting read lock
|
|
commit;
|
|
flush tables;
|
|
drop table t1;
|
|
ERROR HY000: Can't execute the query because you have a conflicting read lock
|
|
unlock tables;
|
|
drop table t1;
|
|
set autocommit=default;
|
|
drop table t2, t3;
|
|
#
|
|
# HANDLER statement and operation-type aware metadata locks.
|
|
# Check that when we clone a ticket for HANDLER we downrade
|
|
# the lock.
|
|
#
|
|
# Establish an auxiliary connection con1.
|
|
# -> connection default
|
|
create table t1 (a int, b int, key a (a));
|
|
insert into t1 (a, b) values (1, 1), (2, 1), (3, 2), (4, 2), (5, 5);
|
|
begin;
|
|
insert into t1 (a, b) values (6, 6);
|
|
handler t1 open;
|
|
handler t1 read a last;
|
|
a b
|
|
6 6
|
|
insert into t1 (a, b) values (7, 7);
|
|
handler t1 read a last;
|
|
a b
|
|
7 7
|
|
commit;
|
|
# -> connection con1
|
|
# Demonstrate that the HANDLER doesn't hold MDL_SHARED_WRITE.
|
|
lock table t1 write;
|
|
unlock tables;
|
|
# -> connection default
|
|
handler t1 read a prev;
|
|
a b
|
|
6 6
|
|
handler t1 close;
|
|
# Cleanup.
|
|
drop table t1;
|
|
# -> connection con1
|
|
# -> connection default
|
|
#
|
|
# A test for Bug#50555 "handler commands crash server in
|
|
# my_hash_first()".
|
|
#
|
|
handler no_such_table read no_such_index first;
|
|
ERROR 42S02: Unknown table 'no_such_table' in HANDLER
|
|
handler no_such_table close;
|
|
ERROR 42S02: Unknown table 'no_such_table' in HANDLER
|
|
#
|
|
# Bug#50907 Assertion `hash_tables->table->next == __null' on
|
|
# HANDLER OPEN
|
|
#
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
CREATE TEMPORARY TABLE t1 (i INT);
|
|
CREATE TEMPORARY TABLE t2 (i INT);
|
|
HANDLER t2 OPEN;
|
|
HANDLER t2 READ FIRST;
|
|
i
|
|
HANDLER t2 CLOSE;
|
|
DROP TABLE t1, t2;
|
|
#
|
|
# Bug#50912 Assertion `ticket->m_type >= mdl_request->type'
|
|
# failed on HANDLER + I_S
|
|
#
|
|
DROP TABLE IF EXISTS t1;
|
|
CREATE TABLE t1 (id INT);
|
|
HANDLER t1 OPEN;
|
|
SELECT table_name, table_comment FROM information_schema.tables
|
|
WHERE table_schema= 'test' AND table_name= 't1';
|
|
table_name table_comment
|
|
t1
|
|
HANDLER t1 CLOSE;
|
|
DROP TABLE t1;
|
|
#
|
|
# Test for bug #50908 "Assertion `handler_tables_hash.records == 0'
|
|
# failed in enter_locked_tables_mode".
|
|
#
|
|
drop tables if exists t1, t2;
|
|
drop function if exists f1;
|
|
create table t1 (i int);
|
|
insert into t1 values (1), (2);
|
|
create table t2 (j int);
|
|
insert into t2 values (1);
|
|
create function f1() returns int return (select count(*) from t2);
|
|
# Check that open HANDLER survives statement executed in
|
|
# prelocked mode.
|
|
handler t1 open;
|
|
handler t1 read next;
|
|
i
|
|
1
|
|
# The below statement were aborted due to an assertion failure.
|
|
select f1() from t2;
|
|
f1()
|
|
1
|
|
handler t1 read next;
|
|
i
|
|
2
|
|
handler t1 close;
|
|
# Check that the same happens under GLOBAL READ LOCK.
|
|
flush tables with read lock;
|
|
handler t1 open;
|
|
handler t1 read next;
|
|
i
|
|
1
|
|
select f1() from t2;
|
|
f1()
|
|
1
|
|
handler t1 read next;
|
|
i
|
|
2
|
|
unlock tables;
|
|
handler t1 close;
|
|
# Now, check that the same happens if LOCK TABLES is executed.
|
|
handler t1 open;
|
|
handler t1 read next;
|
|
i
|
|
1
|
|
lock table t2 read;
|
|
select * from t2;
|
|
j
|
|
1
|
|
unlock tables;
|
|
handler t1 read next;
|
|
i
|
|
2
|
|
handler t1 close;
|
|
# Finally, check scenario with GRL and LOCK TABLES.
|
|
flush tables with read lock;
|
|
handler t1 open;
|
|
handler t1 read next;
|
|
i
|
|
1
|
|
lock table t2 read;
|
|
select * from t2;
|
|
j
|
|
1
|
|
# This unlocks both tables and GRL.
|
|
unlock tables;
|
|
handler t1 read next;
|
|
i
|
|
2
|
|
handler t1 close;
|
|
# Clean-up.
|
|
drop function f1;
|
|
drop tables t1, t2;
|
|
#
|
|
# Test for bug #51136 "Crash in pthread_rwlock_rdlock on TEMPORARY +
|
|
# HANDLER + LOCK + SP".
|
|
# Also see additional coverage for this bug in flush.test.
|
|
#
|
|
drop tables if exists t1, t2;
|
|
create table t1 (i int);
|
|
create temporary table t2 (j int);
|
|
handler t1 open;
|
|
lock table t2 read;
|
|
# This commit should not release any MDL locks.
|
|
commit;
|
|
unlock tables;
|
|
# The below statement crashed before the bug fix as it
|
|
# has attempted to release metadata lock which was
|
|
# already released by commit.
|
|
handler t1 close;
|
|
drop tables t1, t2;
|
|
#
|
|
# Bug#51355 handler stmt cause assertion in
|
|
# bool MDL_context::try_acquire_lock(MDL_request*)
|
|
#
|
|
DROP TABLE IF EXISTS t1;
|
|
# Connection default
|
|
CREATE TABLE t1(id INT, KEY id(id));
|
|
HANDLER t1 OPEN;
|
|
# Connection con51355
|
|
# Sending:
|
|
DROP TABLE t1;
|
|
# Connection default
|
|
# This I_S query will cause the handler table to be closed and
|
|
# the metadata lock to be released. This will allow DROP TABLE
|
|
# to proceed. Waiting for the table to be removed.
|
|
# Connection con51355
|
|
# Reaping: DROP TABLE t1
|
|
# Connection default
|
|
HANDLER t1 READ id NEXT;
|
|
ERROR 42S02: Table 'test.t1' doesn't exist
|
|
HANDLER t1 READ id NEXT;
|
|
ERROR 42S02: Table 'test.t1' doesn't exist
|
|
HANDLER t1 CLOSE;
|
|
# Connection con51355
|
|
# Connection default
|
|
#
|
|
# Bug#54401 assert in Diagnostics_area::set_eof_status , HANDLER
|
|
#
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
DROP FUNCTION IF EXISTS f1;
|
|
CREATE FUNCTION f1() RETURNS INTEGER
|
|
BEGIN
|
|
SELECT 1 FROM t2 INTO @a;
|
|
RETURN 1;
|
|
END|
|
|
SELECT f1();
|
|
ERROR 42S02: Table 'test.t2' doesn't exist
|
|
CREATE TABLE t1(a INT);
|
|
INSERT INTO t1 VALUES (1);
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST WHERE f1() = 1;
|
|
ERROR 42000: This version of MySQL doesn't yet support 'stored functions in HANDLER ... READ'
|
|
HANDLER t1 CLOSE;
|
|
DROP FUNCTION f1;
|
|
DROP TABLE t1;
|
|
#
|
|
# Bug#54920 Stored functions are allowed in HANDLER statements,
|
|
# but broken.
|
|
#
|
|
DROP TABLE IF EXISTS t1;
|
|
DROP FUNCTION IF EXISTS f1;
|
|
CREATE TABLE t1 (a INT);
|
|
INSERT INTO t1 VALUES (1), (2);
|
|
CREATE FUNCTION f1() RETURNS INT RETURN 1;
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST WHERE f1() = 1;
|
|
ERROR 42000: This version of MySQL doesn't yet support 'stored functions in HANDLER ... READ'
|
|
HANDLER t1 CLOSE;
|
|
DROP FUNCTION f1;
|
|
DROP TABLE t1;
|
|
#
|
|
# BUG #46456: HANDLER OPEN + TRUNCATE + DROP (temporary) TABLE, crash
|
|
#
|
|
CREATE TABLE t1 AS SELECT 1 AS f1;
|
|
HANDLER t1 OPEN;
|
|
TRUNCATE t1;
|
|
HANDLER t1 READ FIRST;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
DROP TABLE t1;
|
|
CREATE TEMPORARY TABLE t1 AS SELECT 1 AS f1;
|
|
HANDLER t1 OPEN;
|
|
TRUNCATE t1;
|
|
HANDLER t1 READ FIRST;
|
|
ERROR 42S02: Unknown table 't1' in HANDLER
|
|
DROP TABLE t1;
|
|
#
|
|
# BUG#51877 - HANDLER interface causes invalid memory read
|
|
#
|
|
CREATE TABLE t1(a INT, KEY(a));
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ a FIRST;
|
|
a
|
|
INSERT INTO t1 VALUES(1);
|
|
HANDLER t1 READ a NEXT;
|
|
a
|
|
1
|
|
HANDLER t1 CLOSE;
|
|
DROP TABLE t1;
|
|
#
|
|
# Bug #54007: assert in ha_myisam::index_next , HANDLER
|
|
#
|
|
CREATE TABLE t1(a INT, b INT, PRIMARY KEY(a), KEY b(b), KEY ab(a, b));
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST;
|
|
a b
|
|
HANDLER t1 READ `PRIMARY` NEXT;
|
|
a b
|
|
HANDLER t1 READ ab NEXT;
|
|
a b
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
HANDLER t1 READ NEXT;
|
|
a b
|
|
HANDLER t1 CLOSE;
|
|
INSERT INTO t1 VALUES (2, 20), (1, 10), (4, 40), (3, 30);
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ NEXT;
|
|
a b
|
|
1 10
|
|
HANDLER t1 READ `PRIMARY` NEXT;
|
|
a b
|
|
1 10
|
|
HANDLER t1 READ `PRIMARY` NEXT;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ ab NEXT;
|
|
a b
|
|
1 10
|
|
HANDLER t1 READ ab NEXT;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
1 10
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
3 30
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
4 40
|
|
HANDLER t1 READ b NEXT;
|
|
a b
|
|
HANDLER t1 READ NEXT;
|
|
a b
|
|
4 40
|
|
HANDLER t1 READ NEXT;
|
|
a b
|
|
3 30
|
|
HANDLER t1 READ NEXT;
|
|
a b
|
|
HANDLER t1 CLOSE;
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ `PRIMARY` PREV;
|
|
a b
|
|
4 40
|
|
HANDLER t1 READ `PRIMARY` PREV;
|
|
a b
|
|
3 30
|
|
HANDLER t1 READ b PREV;
|
|
a b
|
|
4 40
|
|
HANDLER t1 READ b PREV;
|
|
a b
|
|
3 30
|
|
HANDLER t1 CLOSE;
|
|
HANDLER t1 OPEN;
|
|
HANDLER t1 READ FIRST;
|
|
a b
|
|
2 20
|
|
HANDLER t1 READ `PRIMARY` PREV LIMIT 3;
|
|
a b
|
|
4 40
|
|
3 30
|
|
2 20
|
|
HANDLER t1 READ b NEXT LIMIT 5;
|
|
a b
|
|
1 10
|
|
2 20
|
|
3 30
|
|
4 40
|
|
HANDLER t1 CLOSE;
|
|
DROP TABLE t1;
|
|
End of 5.1 tests
|