mirror of
https://github.com/MariaDB/server.git
synced 2025-07-28 06:04:59 +02:00
bead24b7f3
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
55 lines
2 KiB
Text
55 lines
2 KiB
Text
use performance_schema;
|
|
set @start_read_only= @@global.read_only;
|
|
create user pfsuser@localhost;
|
|
grant SELECT, UPDATE on performance_schema.* to pfsuser@localhost;
|
|
flush privileges;
|
|
connect con1, localhost, pfsuser, ,"*NO-ONE*";
|
|
connection default;
|
|
set global read_only=0;
|
|
connection con1;
|
|
select @@global.read_only;
|
|
@@global.read_only
|
|
OFF
|
|
show grants;
|
|
Grants for pfsuser@localhost
|
|
GRANT USAGE ON *.* TO `pfsuser`@`localhost`
|
|
GRANT SELECT, UPDATE ON `performance_schema`.* TO `pfsuser`@`localhost`
|
|
# Update on perf_schema is allowed in read_only mode.
|
|
select * from performance_schema.setup_instruments;
|
|
update performance_schema.setup_instruments set enabled='NO';
|
|
update performance_schema.setup_instruments set enabled='YES';
|
|
connection default;
|
|
set global read_only=1;
|
|
connection con1;
|
|
select @@global.read_only;
|
|
@@global.read_only
|
|
ON
|
|
show grants;
|
|
Grants for pfsuser@localhost
|
|
GRANT USAGE ON *.* TO `pfsuser`@`localhost`
|
|
GRANT SELECT, UPDATE ON `performance_schema`.* TO `pfsuser`@`localhost`
|
|
select * from performance_schema.setup_instruments;
|
|
update performance_schema.setup_instruments set enabled='NO';
|
|
ERROR HY000: The MariaDB server is running with the --read-only=ON option so it cannot execute this statement
|
|
update performance_schema.setup_instruments set enabled='YES';
|
|
ERROR HY000: The MariaDB server is running with the --read-only=ON option so it cannot execute this statement
|
|
connection default;
|
|
grant READ_ONLY ADMIN on *.* to pfsuser@localhost;
|
|
flush privileges;
|
|
disconnect con1;
|
|
connect con1, localhost, pfsuser, ,"*NO-ONE*";
|
|
select @@global.read_only;
|
|
@@global.read_only
|
|
ON
|
|
show grants;
|
|
Grants for pfsuser@localhost
|
|
GRANT READ_ONLY ADMIN ON *.* TO `pfsuser`@`localhost`
|
|
GRANT SELECT, UPDATE ON `performance_schema`.* TO `pfsuser`@`localhost`
|
|
select * from performance_schema.setup_instruments;
|
|
update performance_schema.setup_instruments set enabled='NO';
|
|
update performance_schema.setup_instruments set enabled='YES';
|
|
disconnect con1;
|
|
connection default;
|
|
set global read_only= @start_read_only;
|
|
drop user pfsuser@localhost;
|
|
flush privileges;
|