FLUSH PRIVILEGES is used to reload the permission table of MySQL so that manually modified permissions take effect immediately. 1. When directly modifying system tables such as mysql.user or mysql.db, you must execute this command to load the changes from disk to memory; 2. When using standard permission management statement operation permissions such as GRANT, REVOKE, CREATE USER, etc., you do not need to execute this command because the permissions have been automatically refreshed; 3. This command will not restart the service, repair configuration errors, or disconnect the current connection, and only notify MySQL to reread the authorization table content.
Many people will add a sentence after modifying user FLUSH PRIVILEGES
or directly operating the mysql
system library, but do you really know what it does? Simply put, its function is to reload the content of grant tables so that permission-related changes take effect immediately.

MySQL does not monitor the changes in permission tables in real time, so when you manually update system tables such mysql.user
and mysql.db
, if FLUSH PRIVILEGES
is not executed, the new permission settings may not work immediately.
Why do you need FLUSH PRIVILEGES?
MySQL will read permission information into memory when it is started, and subsequent permission judgments are based on data in memory. That is to say, if you use UPDATE
or INSERT
to directly modify the mysql.user
table, these changes only exist on disk and are not loaded into memory by MySQL in real time.
At this time, FLUSH PRIVILEGES
is needed to notify MySQL: "Hey, the system permission table has changed, please reload it."

Common usage scenarios include:
- Modified the user's password
- Added or deleted a user
- Changes permissions at the database or table level
The correct way to use FLUSH PRIVILEGES
Usually we have two ways to make the permission change take effect:

-
Use the GRANT / REVOKE command
- Recommended practice, no need to perform
FLUSH PRIVILEGES
again - Because these commands will automatically trigger permission refresh
- Recommended practice, no need to perform
-
Directly modify the table of mysql system library
- For example, update the
mysql.user
table through SQL - At this time,
FLUSH PRIVILEGES
must be run manually
- For example, update the
For example:
UPDATE mysql.user SET Password = PASSWORD('newpass') WHERE User = 'root'; FLUSH PRIVILEGES;
The above SQL section has modified the password of the root user. If FLUSH PRIVILEGES
is not added, the new password may not take effect immediately.
What does it not do?
Although FLUSH PRIVILEGES
is very useful, it is not omnipotent. Here are some things to note:
- It does not restart MySQL service
- It does not fix permission errors, it just allows the changes that have been made to take effect
- It does not clean up connections or disconnect the current user's session
In addition, some students think that as long as this command is executed, the permission problem will be automatically solved. In fact, this is not the case. If the permissions themselves are configured incorrectly (such as spelling errors or permissions are not granted correctly), it will be useless even if they are refreshed.
Tips: When can I avoid it?
If you operate through standard permission management statements, for example:
GRANT SELECT ON db.* TO 'user'@'host'; REVOKE INSERT ON db.table FROM 'user'@'host'; CREATE USER 'newuser'@'host' IDENTIFIED BY 'password'; DROP USER 'olduser'@'host';
These commands already contain refresh logic inside, and there is no need to manually execute FLUSH PRIVILEGES
.
Basically that's it.
Remember, FLUSH PRIVILEGES
is only required if you bypass GRANT/REVOKE and directly modify the system permission table. Try to use standard statement operation permissions as much as possible, which is safer and worry-free.
The above is the detailed content of mysql flush privileges what it does. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The default user name of MySQL is usually 'root', but the password varies according to the installation environment; in some Linux distributions, the root account may be authenticated by auth_socket plug-in and cannot log in with the password; when installing tools such as XAMPP or WAMP under Windows, root users usually have no password or use common passwords such as root, mysql, etc.; if you forget the password, you can reset it by stopping the MySQL service, starting in --skip-grant-tables mode, updating the mysql.user table to set a new password and restarting the service; note that the MySQL8.0 version requires additional authentication plug-ins.

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

There are three ways to modify or reset MySQLroot user password: 1. Use the ALTERUSER command to modify existing passwords, and execute the corresponding statement after logging in; 2. If you forget your password, you need to stop the service and start it in --skip-grant-tables mode before modifying; 3. The mysqladmin command can be used to modify it directly by modifying it. Each method is suitable for different scenarios and the operation sequence must not be messed up. After the modification is completed, verification must be made and permission protection must be paid attention to.

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB implements repeatable reads through MVCC and gap lock. MVCC realizes consistent reading through snapshots, and the transaction query results remain unchanged after multiple transactions; gap lock prevents other transactions from inserting data and avoids phantom reading. For example, transaction A first query gets a value of 100, transaction B is modified to 200 and submitted, A is still 100 in query again; and when performing scope query, gap lock prevents other transactions from inserting records. In addition, non-unique index scans may add gap locks by default, and primary key or unique index equivalent queries may not be added, and gap locks can be cancelled by reducing isolation levels or explicit lock control.

Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation
