Search Results
https://dev.mysql.com/doc/refman/8.4/en/account-categories.html
MySQL incorporates the concept of user account categories, based on the SYSTEM_USER privilege. The SYSTEM_USER privilege has an effect on the accounts to which a given user can apply its other privileges, as well as whether the user is protected ...
https://dev.mysql.com/doc/refman/8.4/en/change-replication-source-to.html
If you disable GTID_ONLY after setting it, the existing relay logs are deleted and the existing known binary log file positions are persisted, even if they are stale. Log rotation and deletion events from the servers are not ignored, and are ...] ...
https://dev.mysql.com/doc/refman/8.4/en/create-event.html
CREATE [DEFINER = user] EVENT [IF NOT EXISTS] event_name ON SCHEDULE schedule [ON COMPLETION [NOT] PRESERVE] [ENABLE | DISABLE | DISABLE ON {REPLICA | SLAVE}] [COMMENT 'string'] DO event_body; schedule: { AT timestamp [+ INTERVAL interval] ... The ...
https://dev.mysql.com/doc/refman/8.4/en/extensions-to-ansi.html
The ORDER BY and LIMIT clauses of the UPDATE and DELETE statements. The LOW_PRIORITY clause of the INSERT, REPLACE, DELETE, and UPDATE statements. MySQL Server supports some extensions that you are not likely to find in other SQL DBMSs. Be warned ...
https://dev.mysql.com/doc/refman/8.4/en/firewall-usage.html
Firewall mode-setting operations also permit a mode value of RESET, but this value is not stored: setting a profile to RESET mode causes the firewall to delete all rules for the profile and set its mode to OFF. Before using MySQL Enterprise ...
https://dev.mysql.com/doc/refman/8.4/en/information-functions.html
This applies to statements such as UPDATE, INSERT, or DELETE (as before), but now also to statements such as ALTER TABLE and LOAD DATA. For REPLACE statements, the affected-rows value is 2 if the new row replaced an old row, because in this case, ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-tablestats-table.html
Table statistics are updated only for DELETE or UPDATE operations that modify indexed columns. The value could be imprecise if uncommitted transactions are inserting into or deleting from the table. MODIFIED_COUNTER The number of rows modified by ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-trx-table.html
The value might include delete-marked rows that are physically present but not visible to the transaction. The INNODB_TRX table provides information about every transaction currently executing inside InnoDB, including whether the transaction is ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
Since MySQL can “delete-mark” and delete rows on compressed pages “in place” by modifying uncompressed data, DELETE operations on a table are relatively efficient. Most often, the internal optimizations described in InnoDB Data Storage and ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks-handling.html
You can get deadlocks even in the case of transactions that just insert or delete a single row. That is because these operations are not really “atomic”; they automatically set locks on the (possibly several) index records of the row inserted or ... This section builds on the conceptual information about deadlocks in Section 17.7.5.2, “Deadlock ...