PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-statement-tables.html
For row-based replication, table I/O done on the replica as it processes row changes can be instrumented, but row events in the relay log do not appear as discrete statements. Statement events occur at a high level of the event hierarchy. Within the ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-user-defined-functions-table.html
The user_defined_functions table contains a row for each loadable function registered automatically by a component or plugin, or manually by a CREATE FUNCTION statement. For information about operations that add or remove table rows, see Section ...
https://dev.mysql.com/doc/refman/8.0/en/problems-with-null.html
The following statement returns no rows, because expr = NULL is never true for any expression: mysql> SELECT * FROM my_table WHERE phone = NULL; To look for NULL values, you must use the IS NULL test. The exception to this is COUNT(*), which counts ... The concept of the NULL value is a common source of confusion for newcomers to SQL, who often think that NULL is the same thing as an empty string ...
https://dev.mysql.com/doc/refman/8.0/en/repeat.html
[begin_label:] REPEAT statement_list UNTIL search_condition END REPEAT [end_label] The statement list within a REPEAT statement is repeated until the search_condition expression is true. statement_list consists of one or more statements, each ...
https://dev.mysql.com/doc/refman/8.0/en/replication-compatibility.html
A source might also have optional features enabled that are not understood by older replicas, such as binary log transaction compression, where the resulting compressed transaction payloads cannot be read by a replica at a release before MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-blackhole.html
Updates and deletes are handled differently depending on whether statement based or row based logging is in use. When using row-based logging, updates and deletes to such tables are simply skipped—they are not written to the binary log. For this ... The BLACKHOLE storage engine accepts data but discards it and does not store ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-checksum-table.html
CHECKSUM TABLE returns a checksum that is calculated row by row, using a method that depends on the table row storage format. The storage format is not guaranteed to remain the same between MySQL versions, so the checksum value might change ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features.html
You can avoid these issues by using MySQL's row-based replication instead. For more information about row-based logging and row-based replication, see Section 7.4.4.1, “Binary Logging Formats”, and Section 19.2.1, “Replication Formats”. The ...
https://dev.mysql.com/doc/refman/8.0/en/replication-threads-monitor-main.html
row *************************** Id: 2 User: root Host: localhost:32931 db: NULL Command: Binlog Dump Time: 94 State: Has sent all binlog to slave; waiting for binlog to be updated Info: NULL Here, thread 2 is a Binlog Dump thread that services a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-upgrade.html
Alternatively, if you cannot stop new statements, temporarily change to row-based logging on the source (binlog_format=ROW) and wait until all replicas have processed all binary logs produced up to the point of this change, then upgrade the replicas. If you made a temporary change to row-based logging or to the default character set, you can revert the change ... When you upgrade servers that participate in a replication ...