Search Results
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-update-loaded-data.html
You can update loaded external tables by using one of the following methods: You can load data from Object Storage by using event-based incremental load. To prevent the data in a Lakehouse table from getting outdated, refresh the tables using ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-replication-group-members.html
The performance_schema.replication_group_members table is used for monitoring the status of the different server instances that are members of the group. The information in the table is updated whenever there is a view change, for example when the ...At that point, servers exchange some of their metadata to synchronize themselves and continue to cooperate ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-disk-data.html
NDB Cluster supports storing nonindexed columns of NDB tables on disk, rather than in RAM. Column data and logging metadata are kept in data files and undo log files, conceptualized as tablespaces and log file groups, as described in the next ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-files.html
The files table is empty if no disk data objects have been created in NDB. See Section 25.6.11.1, “NDB Cluster Disk Data Objects”, for more information.
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-logspaces.html
This table provides information about NDB Cluster log space usage. The logspaces table contains the following columns: node_id The ID of this data node. node_id The log ID; for Disk Data undo log files, this is the same as the value shown in the ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-restart-info.html
Each entry in the table corresponds to a node restart status report in real time from a data node with the given node ID. The restart_info table contains the following columns: node_id Node ID in the cluster node_restart_status Node status; see text ...Only the most recent report for any given node is ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-tc-time-track-stats.html
The tc_time_track_stats table provides time-tracking information obtained from the DBTC block (TC) instances in the data nodes, through API nodes access NDB. index_key_ops Based on duration of successful unique index key operations, tracked against ...Each TC instance tracks latencies for a set of activities it undertakes on behalf of API nodes or other data nodes; these activities include transactions, transaction errors, key reads, key writes, unique index operations, failed key operations of any type, scans, failed scans, fragment scans, and failed fragment ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-threadblocks.html
The threadblocks table associates data nodes, threads, and instances of NDB kernel blocks. The threadblocks table contains the following columns: node_id Node ID thr_no Thread ID block_name Block name block_instance Block instance number Notes The ...Although the list of possible values is static for a given NDB Cluster release, the list may vary between ...
https://dev.mysql.com/doc/refman/8.4/en/mysqldump-definition-data-dumps.html
The --no-data option tells mysqldump not to dump table data, resulting in the dump file containing only statements to create the tables. Conversely, the --no-create-info option tells mysqldump to suppress CREATE statements from the output, so that ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-blackhole.html
When performing binary logging, all inserts to such tables are always logged, regardless of the logging format in use. With the statement based logging format, all statements affecting BLACKHOLE tables are logged, but their effects ignored. When ...