PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-options-variables.html
Ndb_conflict_fn_max Used in NDB Cluster Replication conflict resolution, this variable shows the number of times that a row was not applied on the current SQL node due to “greatest timestamp wins” conflict resolution since the last time that ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-programs-ndb-mgmd.html
--ndb-log-timestamps Command-Line Format --ndb-log-timestamps Type Enumeration Default Value UTC Valid Values LEGACYUTCSYSTEM Sets the format used for timestamps in node logs. The management server is the process that reads the cluster ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-programs-ndbd.html
--ndb-log-timestamps Command-Line Format --ndb-log-timestamps Type Enumeration Default Value UTC Valid Values LEGACYUTCSYSTEM Sets the format used for timestamps in node logs. The ndbd binary provides the single-threaded version of the process that ...
https://dev.mysql.com/doc/refman/9.7/en/mysqlbinlog-hexdump.html
For more information about binary log format, see MySQL Internals: The Binary Log. In the example shown, '9d fc 5c 43' is the representation of '051024 17:24:13' in hexadecimal. Master ID: The server ID of the replication source server that created ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-ndb-replication-applier-status-table.html
CONFLICT_FN_MAX: The number of times that NDB replication “greater timestamp wins” conflict resolution has been applied to update and delete operations. CONFLICT_FN_OLD: The number of times that NDB replication “same timestamp wins” conflict ... NDBCLUSTER exposes its internal replication applier state for observation using global status variables such as Ndb_replica_max_replicated_epoch and Ndb_api_trans_start_count_replica, but these values reflect the state of the default replication channel ...
https://dev.mysql.com/doc/refman/9.7/en/point-in-time-recovery-positions.html
Because the output of mysqlbinlog includes SET TIMESTAMP statements before each SQL statement recorded, the recovered data and related MySQL logs reflect the original times at which the transactions were executed. The last section, Section 9.5.1, ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-functions.html
(You can consider the function execution timestamp and random number seed as implicit inputs that are identical on the source and replica.) The FOUND_ROWS() and ROW_COUNT() functions are not replicated reliably using statement-based replication.
https://dev.mysql.com/doc/refman/9.7/en/storage-requirements.html
Leftover Digits Number of Bytes 0 0 1 1 2 1 3 2 4 2 5 3 6 3 7 4 8 4 Date and Time Type Storage Requirements For TIME, DATETIME, and TIMESTAMP columns, the storage required for tables created before MySQL 5.6.4 differs from tables created from 5.6.4 ... InnoDB Table Storage Requirements NDB Table Storage Requirements Numeric Type Storage Requirements Date and Time Type Storage Requirements String Type Storage Requirements Spatial Type Storage Requirements JSON Storage Requirements The storage requirements for table data on disk depend on several ...
https://dev.mysql.com/doc/refman/9.7/en/using-date.html
MySQL also permits a “relaxed” string format when updating and in a WHERE clause that compares a date to a DATE, DATETIME, or TIMESTAMP column. When you compare a DATE, TIME, DATETIME, or TIMESTAMP to a constant string with the <, <=, =, >=, >, ...You should use this format in UPDATE expressions and in the WHERE clause of SELECT ...
https://dev.mysql.com/doc/refman/9.7/en/alter-table-examples.html
For NDB tables, it is also possible to change the storage type used for a table or column. row *************************** Table: t1 Create Table: CREATE TABLE `t2` ( `c1` int(11) DEFAULT NULL ) /*!50100 TABLESPACE ts_1 STORAGE DISK */ ...