mariadb/mysql-test/suite/handler
Sergei Golubchik bead24b7f3 mariadb-test: wait on disconnect
Remove one of the major sources of race condiitons in mariadb-test.
Normally, mariadb_close() sends COM_QUIT to the server and immediately
disconnects. In mariadb-test it means the test can switch to another
connection and sends queries to the server before the server even
started parsing the COM_QUIT packet and these queries can see the
connection as fully active, as it didn't reach dispatch_command yet.

This is a major source of instability in tests and many - but not all,
still less than a half - tests employ workarounds. The correct one
is a pair count_sessions.inc/wait_until_count_sessions.inc.
Also very popular was wait_until_disconnected.inc, which was completely
useless, because it verifies that the connection is closed, and after
disconnect it always is, it didn't verify whether the server processed
COM_QUIT. Sadly the placebo was as widely used as the real thing.

Let's fix this by making mariadb-test `disconnect` command _to wait_ for
the server to confirm. This makes almost all workarounds redundant.

In some cases count_sessions.inc/wait_until_count_sessions.inc is still
needed, though, as only `disconnect` command is changed:

 * after external tools, like `exec $MYSQL`
 * after failed `connect` command
 * replication, after `STOP SLAVE`
 * Federated/CONNECT/SPIDER/etc after `DROP TABLE`

and also in some XA tests, because an XA transaction is dissociated from
the THD very late, after the server has closed the client connection.

Collateral cleanups: fix comments, remove some redundant statements:
 * DROP IF EXISTS if nothing is known to exist
 * DROP table/view before DROP DATABASE
 * REVOKE privileges before DROP USER
 etc
2025-07-16 09:14:33 +07:00
..
aria.result mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
aria.test MDEV-20207: Assertion ! is_set() failed in Diagnostics_area::set_eof_status 2022-04-26 12:40:11 +05:30
disconnect_4480.result
disconnect_4480.test
handler.inc mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
handler_warnings.result MDEV-30263 Assertion failure in Protocol::end_statement upon HANDLER READ with invalid timestamp 2024-12-13 16:27:14 +01:00
handler_warnings.test MDEV-30263 Assertion failure in Protocol::end_statement upon HANDLER READ with invalid timestamp 2024-12-13 16:27:14 +01:00
heap.result mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
heap.test MDEV-15813 ASAN use-after-poison in hp_hashnr upon HANDLER READ on a versioned HEAP table. 2018-05-16 09:44:22 +04:00
init.inc MDEV-18650: Options deprecated in previous versions - storage_engine 2020-02-13 13:42:01 +02:00
innodb.result mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
innodb.test Merge branch '10.4' into 10.5 2022-05-09 22:04:06 +02:00
interface.result mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
interface.test mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
myisam.result mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00
myisam.test MDEV-20207: Assertion ! is_set() failed in Diagnostics_area::set_eof_status 2022-04-26 12:40:11 +05:30
ps.result MDEV-15729 Server crashes in Field::make_field upon HANDLER READ executed with PS protocol 2018-06-11 09:57:54 +02:00
ps.test MDEV-31005: Make working cursor-protocol 2024-09-18 18:39:26 +07:00
savepoint.inc mariadb-test: wait on disconnect 2025-07-16 09:14:33 +07:00