MySQL Bugs: #9740: MAX_QUERIES_PER

Bug #9740	MAX_QUERIES_PER_HOUR issues
Submitted:	8 Apr 2005 0:48	Modified:	27 Dec 2006 14:12
Reporter:	dennis bertani	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.11	OS:
Assigned to:		CPU Architecture:	Any

Description:
Hello,

please refer to bug #8350

The problem with MAX_QUERIES_PER_HOUR still persists in 4.1.11 release when a user hits his limit he cannot execute any query until the server is restarted or a flush user_resources command is issued.

Thanks in advance for your attention.

How to repeat:
See above

Suggested fix:
Manually restarting the server or flushing user resources.

Please, try with a newer version (I'd recommend 4.1.14) and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

conn1> CREATE USER 'user1'@'localhost';
Query OK, 0 rows affected (0.00 sec)

conn1> GRANT SELECT ON world.city TO user1@'localhost' with max_queries_per_hour 2;
Query OK, 0 rows affected (0.00 sec)

flupps:~ flupps$ mysql -u user1 -p
Enter password: 
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 37 to server version: 5.0.24a-max-log

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

conn2> SELECT * FROM City LIMIT 1;
ERROR 1226 (42000): User 'user1' has exceeded the 'max_questions' resource (current value: 2)

conn1> GRANT SELECT ON world.city TO user1@'localhost' with max_queries_per_hour 100000;
Query OK, 0 rows affected (0.00 sec)

conn1> show grants for user1@localhost;
+----------------------------------------------------------------------------+
| Grants for user1@localhost                                                 |
+----------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'user1'@'localhost' WITH MAX_QUERIES_PER_HOUR 100000 | 
| GRANT SELECT ON `world`.`city` TO 'user1'@'localhost'                      | 
+----------------------------------------------------------------------------+
2 rows in set (0.00 sec)

conn2> \r
Connection id:    38
Current database: world

conn2> SELECT * FROM City LIMIT 1;
ERROR 1226 (42000): User 'user1' has exceeded the 'max_questions' resource (current value: 2)

Flush privileges works, but that resets ALL users' query counters.

Please, try with a newr versions, 4.1.21 and 5.0.27, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".