Search Results
https://dev.mysql.com/doc/refman/8.4/en/server-options.html
--super-large-pages Command-Line Format --super-large-pages[={OFF|ON}] Platform Specific Solaris Type Boolean Default Value OFF Standard use of large pages in MySQL attempts to use the largest size supported, up to 4MB. This means that when you ...
https://dev.mysql.com/doc/ndbapi/en/ndb-error-codes-schema-error.html
The following list enumerates all NDB errors of type SE (Schema error).
https://dev.mysql.com/doc/refman/8.4/en/load-data.html
Some cases are not supported by LOAD DATA: Fixed-size rows (FIELDS TERMINATED BY and FIELDS ENCLOSED BY both empty) and BLOB or TEXT columns. With IGNORE, new rows that duplicate an existing row on a unique key value are discarded. Suppose that you ...The file can be read from the server host or the client host, depending on whether the LOCAL modifier is ...
https://dev.mysql.com/doc/mysql-monitor/8.0/en/performance-advisors-ref.html
Excessive Disk Temporary Table Usage Detected If the space required to build a temporary table exceeds either tmp_table_size or max_heap_table_size, MySQL creates a disk-based table in the server's tmpdir directory. For performance reasons it is ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-memory-per-fragment.html
Each variable-sized page is reorganized as needed to fit the changing size of variable-sized row parts as they are inserted, updated, and deleted; if a given row part grows too large for the page it is in, it can be moved to a different page. These ...This is true as long as all data nodes are running and connected to the cluster; for a data node that is missing, there are no rows for the fragment replicas that it ...
https://dev.mysql.com/doc/refman/8.4/en/memory-use.html
If an internal in-memory temporary table becomes too large (as determined by tmp_table_size and max_heap_table_size), MySQL automatically converts the table from in-memory to on-disk format, which uses the InnoDB storage engine. For MEMORY tables ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-internals.html
If you create a table when innodb_strict_mode is OFF, and a subsequent INSERT or UPDATE statement attempts to create an index entry that does not fit in the size of the compressed page, the operation fails with ERROR 42000: Row size too large. If ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
The sum of file sizes must be, at a minimum, slightly larger than 12MB. The following configuration permits ibdata1 to grow to a limit of 500MB: [mysqld] innodb_data_file_path=ibdata1:12M:autoextend:max:500M A minimum file size is enforced for the ... The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-conflict-resolution.html
Note If you are replicating tables with very large columns (such as TEXT or BLOB columns), --ndb-log-updated-only can also be useful for reducing the size of the binary logs and avoiding possible replication failures due to exceeding ...Conflict ...
https://dev.mysql.com/doc/internals/en/event-data-for-specific-event-types.html
Log files created subsequently (when someone issues a FLUSH LOGS statement or the current binary log file becomes too large) do not contain this event. SELECT fails after inserting 1000 rows into a MyISAM table (for example, with a duplicate-key ...