| Bug #81860 | read_only is not allowed for SUPER because of prelocking | ||
|---|---|---|---|
| Submitted: | 15 Jun 2016 10:18 | Modified: | 15 Jun 2016 11:36 |
| Reporter: | Sergei Golubchik | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
[15 Jun 2016 10:18]
Sergei Golubchik
[15 Jun 2016 11:36]
MySQL Verification Team
Hello Sergei, Thank you for the report and test case. Thanks, Umesh
[15 Jun 2016 11:37]
MySQL Verification Team
-- 5.6.31/32
main.81860 [ fail ]
Test ended at 2016-06-15 13:14:26
CURRENT_TEST: main.81860
mysqltest: At line 17: query 'select test.f1()' failed: 1370: execute command denied to user 'foo'@'localhost' for routine 'test.f1'
-- 5.7.13/14
set global read_only=1;
main.81860 [ fail ]
Test ended at 2016-06-15 13:32:47
CURRENT_TEST: main.81860
mysqltest: At line 17: query 'select test.f1()' failed: 1370: execute command denied to user 'foo'@'localhost' for routine 'test.f1'
safe_process[28377]: Child process: 28378, exit: 1
-- 5.5.50
set global read_only=1;
main.81860 [ fail ]
Test ended at 2016-06-15 13:33:18
CURRENT_TEST: main.81860
mysqltest: At line 17: query 'select test.f1()' failed: 1290: The MySQL server is running with the --read-only option so it cannot execute this statement
