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/mysql-cluster-ndbinfo-table-distribution-status.html
The table_distribution_status table provides information about the progress of table distribution for NDB tables. is_reorg_ongoing Whether the table is currently being reorganized (1 if true) .
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-upgrade-downgrade.html
Do not use ALTER TABLE on any existing NDB tables; do not create any new NDB tables which cannot be safely dropped prior to downgrading. After backing up the state data, drop all NDB tables which have been created or altered since the upgrade took ... Versions Supported for Upgrade to NDB 8.0 Reverting an NDB Cluster 8.0 Upgrade Known Issues When Upgrading or Downgrading NDB Cluster This section provides information about NDB Cluster software and compatibility between different NDB Cluster 8.0 releases with regard to performing upgrades and ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-list.html
(Using ALTER TABLE employees DROP PARTITION pWest would also delete all of these rows, but would also remove the partition pWest from the definition of the table; you would need to use an ALTER TABLE ... List partitioning in MySQL is similar to ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-clone-progress-table.html
The stages of a cloning operation include DROP DATA, FILE COPY, PAGE_COPY, REDO_COPY, FILE_SYNC, RESTART, and RECOVERY. Stages include DROP DATA, FILE COPY, PAGE_COPY, REDO_COPY, FILE_SYNC, RESTART, and RECOVERY. Note The Performance Schema table ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-auto-increment.html
Regardless of the method used to create and populate the copy having the AUTO_INCREMENT column, the final step is to drop the original table and then rename the copy: DROP t1; ALTER TABLE t2 RENAME t1; See also Section B.3.6.1, “Problems with ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-temptables.html
In statement-based replication mode, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside a transaction, procedure, function, or trigger when GTIDs are in use on the server (that is, when the enforce_gtid_consistency ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
If triggers for the table are added or dropped subsequent to the downgrade, the server rewrites the table's .TRG file. With statement-based replication, triggers executed on the source also execute on the replica. With row-based replication, ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-restrictions.html
When binlog_format is set to STATEMENT, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside transactions, procedures, functions, and triggers when GTIDs are in use on the server (that is, when the ... Because GTID-based ...
https://dev.mysql.com/doc/refman/8.0/en/show-profile.html
Note The SHOW PROFILE and SHOW PROFILES statements are deprecated; expect them to be removed in a future MySQL release. Use the Performance Schema instead; see Section 29.19.1, “Query Profiling Using Performance Schema”. To control profiling, ...
https://dev.mysql.com/doc/refman/8.0/en/show-warnings.html
SHOW WARNINGS [LIMIT [offset,] row_count] SHOW COUNT(*) WARNINGS SHOW WARNINGS is a diagnostic statement that displays information about the conditions (errors, warnings, and notes) resulting from executing a statement in the current session.