Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-status-monitoring.html
Names for these variables have several forms: Performance_schema_xxx_classes_lost indicates how many instruments of type xxx could not be loaded. Performance_schema_xxx_instances_lost indicates how many instances of object type xxx could not be ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-user-variable-tables.html
The Performance Schema provides a user_variables_by_thread table that exposes user-defined variables. These are variables defined within a specific session and include a @ character preceding the name; see Section 11.4, “User-Defined Variables”. The user_variables_by_thread table has these columns: THREAD_ID The thread identifier of the session in which the variable is ...
https://dev.mysql.com/doc/refman/8.4/en/prepare.html
PREPARE stmt_name FROM preparable_stmt The PREPARE statement prepares a SQL statement and assigns it a name, stmt_name, by which to refer to the statement later. The prepared statement is executed with EXECUTE and released with DEALLOCATE PREPARE.
https://dev.mysql.com/doc/refman/8.4/en/privileges-provided.html
The privileges granted to a MySQL account determine which operations the account can perform. MySQL privileges differ in the contexts in which they apply and at different levels of operation: Administrative privileges enable users to manage ...
https://dev.mysql.com/doc/refman/8.4/en/problems-with-float.html
Floating-point numbers sometimes cause confusion because they are approximate and not stored as exact values. A floating-point value as written in an SQL statement may not be the same as the value represented internally. Attempts to treat ...
https://dev.mysql.com/doc/refman/8.4/en/program-variables.html
Many MySQL programs have internal variables that can be set at runtime using the SET statement. See Section 15.7.6.1, “SET Syntax for Variable Assignment”, and Section 7.1.9, “Using System Variables”. Most of these program variables also ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-sql-mode.html
Using different server SQL mode settings on the source and the replica may cause the same INSERT statements to be handled differently on the source and the replica, leading the source and replica to diverge. For best results, you should always use ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-transactions.html
In general, you should avoid transactions that update both transactional and nontransactional tables in a replication environment. You should also avoid using any statement that accesses both transactional (or temporary) and nontransactional tables ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...