Search

Download this Manual
PDF (US Ltr) - 43.2Mb
PDF (A4) - 43.3Mb
Man Pages (TGZ) - 295.2Kb
Man Pages (Zip) - 400.4Kb
Info (Gzip) - 4.3Mb
Info (Zip) - 4.3Mb


Displaying 411 to 420 of 1832 total results
https://dev.mysql.com/doc/refman/8.0/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 ...The server uses these rules for binary logging: If the initial statements in a transaction are nontransactional, they are written to the binary log ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-security-mysql-privileges.html
The only tables that would be safe from this sort of mayhem would be those tables that were created using storage engines other than NDB, and so not visible to a “rogue” SQL node. This includes all MySQL privilege types (SELECT privilege, UPDATE ... In this section, we discuss how the MySQL privilege system works in relation to NDB Cluster and the implications of this for keeping an NDB Cluster ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
A GTID is also assigned to the creation, alteration, or deletion of a database, and of a non-table database object such as a procedure, function, trigger, event, view, user, role, or grant. One GTID is generated for the CREATE TABLE action and one ...Whenever the binary log is rotated or the server is shut down, the server writes GTIDs for all transactions that were written into the previous binary log file into the mysql.gtid_executed ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-list.html
For more detailed syntactical information, see Section 15.1.20, “CREATE TABLE Statement”. As with the other partitioning examples, we assume that the default_storage_engine is InnoDB.) Suppose that there are 20 video stores distributed among 4 ... List partitioning in MySQL is similar to range partitioning in many ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-usage.html
In addition, because temporary tables can be read only from the thread which created them, there is seldom if ever any benefit obtained from replicating them, even when using statement-based format. You can switch from statement-based to row-based ...As noted in Section 19.5.1.31, “Replication and Temporary Tables”, temporary tables are not replicated when using row-based format or (from MySQL 8.0.4) mixed ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-tp-thread-group-state-table.html
Note As of MySQL 8.0.14, the thread pool INFORMATION_SCHEMA tables are also available as Performance Schema tables. (See Section 29.12.16, “Performance Schema Thread Pool Tables”.) The INFORMATION_SCHEMA tables are deprecated; expect them to be ...Each row provides information about the current state of a ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-tp-thread-group-stats-table.html
Note As of MySQL 8.0.14, the thread pool INFORMATION_SCHEMA tables are also available as Performance Schema tables. (See Section 29.12.16, “Performance Schema Thread Pool Tables”.) The INFORMATION_SCHEMA tables are deprecated; expect them to be ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-stages-history-table.html
The events_stages_history table contains the N most recent stage events that have ended per thread. Stage events are not added to the table until they have ended. When the table contains the maximum number of rows for a given thread, the oldest ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-statements-history-table.html
The events_statements_history table contains the N most recent statement events that have ended per thread. Statement events are not added to the table until they have ended. When the table contains the maximum number of rows for a given thread, ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-transactions-history-table.html
The events_transactions_history table contains the N most recent transaction events that have ended per thread. Transaction events are not added to the table until they have ended. When the table contains the maximum number of rows for a given ...
Displaying 411 to 420 of 1832 total results