mirror of
https://github.com/MariaDB/server.git
synced 2025-07-19 17:58:24 +02:00
ce8a74f235
The main purpose of this allow one to use the --read-only option to ensure that no one can issue a query that can block replication. The --read-only option can now take 4 different values: 0 No read only (as before). 1 Blocks changes for users without the 'READ ONLY ADMIN' privilege (as before). 2 Blocks in addition LOCK TABLES and SELECT IN SHARE MODE for not 'READ ONLY ADMIN' users. 3 Blocks in addition 'READ_ONLY_ADMIN' users for all the previous statements. read_only is changed to an enum and one can use the following names for the lock levels: OFF, ON, NO_LOCK, NO_LOCK_NO_ADMIN Too keep things compatible with older versions config files, one can still use values FALSE and TRUE, which are mapped to OFF and ON. The main visible changes are: - 'show variables like "read_only"' now returns a string instead of a number. - Error messages related to read_only violations now contains the current value off readonly. Other things: - is_read_only_ctx() renamed to check_read_only_with_error() - Moved TL_READ_SKIP_LOCKED to it's logical place Reviewed by: Sergei Golubchik <serg@mariadb.org>
21 lines
572 B
Text
21 lines
572 B
Text
#
|
|
# Bug#58669: read_only not enforced on 5.5.x
|
|
#
|
|
CREATE USER user1@localhost;
|
|
CREATE DATABASE db1;
|
|
GRANT ALL PRIVILEGES ON db1.* TO user1@localhost;
|
|
CREATE TABLE db1.t1(a INT);
|
|
connect con1,localhost,user1,,;
|
|
connection con1;
|
|
SELECT CURRENT_USER();
|
|
CURRENT_USER()
|
|
user1@localhost
|
|
SHOW VARIABLES LIKE "read_only%";
|
|
Variable_name Value
|
|
read_only ON
|
|
INSERT INTO db1.t1 VALUES (1);
|
|
ERROR HY000: The MariaDB server is running with the --read-only=ON option so it cannot execute this statement
|
|
connection default;
|
|
disconnect con1;
|
|
DROP DATABASE db1;
|
|
DROP USER user1@localhost;
|