PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysqlbinlog-row-events.html
These correspond to events with the WRITE_ROWS_EVENT, UPDATE_ROWS_EVENT, and DELETE_ROWS_EVENT type codes. # at 302 #080828 15:03:08 server id 1 end_log_pos 356 Update_rows: table id 17 flags: STMT_END_F BINLOG ' ... The following examples ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-transaction-management.html
Avoid performing rollbacks after inserting, updating, or deleting huge numbers of rows. Set innodb_change_buffering=all so that update and delete operations are buffered in addition to inserts. Consider issuing COMMIT statements periodically during ... To optimize InnoDB transaction processing, find the ideal balance between the performance overhead of transactional features and the workload of your ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-selection.html
SQL statements supporting explicit partition selection are listed here: SELECT DELETE INSERT REPLACE UPDATE LOAD DATA. Explicit selection of partitions and subpartitions for rows matching a given WHERE condition is supported. Partition selection is ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-memory-summary-tables.html
Operation counts help to understand or tune the overall pressure the server is putting on the memory allocator, which has an impact on performance. Allocating a single byte one million times is not the same as allocating one million bytes a single ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-statement-tables.html
Statement events occur at a high level of the event hierarchy. Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store statement events: ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-wait-tables.html
The Performance Schema instruments waits, which are events that take time. Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store wait events: ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-errors.html
For nontransactional storage engines such as MyISAM, it is possible to have a statement that only partially updates a table and returns an error code. This can happen, for example, on a multiple-row insert that has one row violating a key ... If a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-row-searches.html
When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching rows. If the algorithm is able to select a primary key or a unique index where every column in the index has ...The algorithm used to carry out this process uses one of the table's indexes to carry out the search as the first choice, and a hash table if there are no suitable ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
A transaction which updates non-transactional tables has applied some but not all of its changes. Up to and including MySQL 8.0.18, preserving the commit order requires that binary logging (log_bin) and replica update logging (log_replica_updates or ... Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks-account.html
The REPLICATION_APPLIER privilege explicitly or implicitly allows the PRIVILEGE_CHECKS_USER account to carry out the following operations that a replication thread needs to perform: Setting the value of the system variables gtid_next, ... The user ...