Bug #93259 Docs unclear regarding need for FLUSH PRIVILEGES after ALTER USER
Submitted: 20 Nov 2018 12:45 Modified: 22 Nov 2018 12:51
Reporter: Eric Herman (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.7, 8.0 OS:Any
Assigned to: CPU Architecture:Any

[20 Nov 2018 12:45] Eric Herman 
Description:
Docs ( https://dev.mysql.com/doc/refman/8.0/en/privilege-changes.html ) clearly state that FLUSH PRIVILEGES is not required after RENAME USER, but is required after UPDATE. What about ALTER USER?

How to repeat:
read https://dev.mysql.com/doc/refman/8.0/en/privilege-changes.html
[20 Nov 2018 12:55] MySQL Verification Team 
Hello Eric,

Thank you for the report!

regards,
Umesh
[21 Nov 2018 22:25] Paul DuBois 
I'm not clear why this bug was filed:

Are you suggesting that FLUSH PRIVILEGES *is* needed after ALTER USER, or are you suggesting that it's not clear from the page *whether* FLUSH PRIVILEGES is needed after ALTER USER?

Thanks.
[22 Nov 2018 12:51] Paul DuBois 
Posted by developer:
 
On the supposition that the docs were unclear, I've modified as follows:

If you modify the grant tables indirectly an account-management statement, the server notices these changes and loads the grant tables into memory again immediately. Account-management statements are described in Section 13.7.1, “Account Management Statements”. Examples include GRANT, REVOKE, SET PASSWORD, and RENAME USER.