PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/archive-storage-engine.html
The ARCHIVE storage engine produces special-purpose tables that store large amounts of unindexed data in a very small footprint. There are several types of insertions that are used: An INSERT statement just pushes rows into a compression buffer, ...
https://dev.mysql.com/doc/refman/8.0/en/index-btree-hash.html
One circumstance under which this occurs is when the optimizer estimates that using the index would require MySQL to access a very large percentage of the rows in the table. For example, the following SELECT statements use indexes: SELECT * FROM ...
https://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html
Dropping and re-adding an index can be expensive for a large table, whereas making it invisible and visible are fast, in-place operations. row *************************** id: 1 select_type: SIMPLE table: t1 partitions: NULL type: range ... MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html
After deleting a large part of a MyISAM or ARCHIVE table, or making many changes to a MyISAM or ARCHIVE table with variable-length rows (tables that have VARCHAR, VARBINARY, BLOB, or TEXT columns). Deleted rows are maintained in a linked list and ...
https://dev.mysql.com/doc/refman/8.0/en/analyze-table.html
This makes ANALYZE TABLE fast on InnoDB tables but not 100% accurate because it does not take all rows into account. row *************************** SCHEMA_NAME: mydb TABLE_NAME: t COLUMN_NAME: c1 HISTOGRAM: {"buckets": [[206, 0.0625], [456, 0.125], ...ANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name UPDATE HISTOGRAM ON col_name [, col_name] ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-setup-instruments-table.html
row *************************** NAME: wait/synch/mutex/pfs/LOCK_pfs_share_list ENABLED: NO TIMED: NO PROPERTIES: singleton FLAGS: NULL VOLATILITY: 1 DOCUMENTATION: Components can provide their own performance_schema tables. row ... The ...
https://dev.mysql.com/doc/refman/8.0/en/checksum-table.html
Performance Considerations By default, the entire table is read row by row and the checksum is calculated. For large tables, this could take a long time, thus you would only perform this operation occasionally. This row-by-row calculation is what ...
https://dev.mysql.com/doc/refman/8.0/en/example-auto-increment.html
For example: INSERT INTO animals (id,name) VALUES(NULL,'squirrel'); When you insert any other value into an AUTO_INCREMENT column, the column is set to that value and the sequence is reset so that the next automatically generated value follows ...
https://dev.mysql.com/doc/refman/8.0/en/faqs-replication.html
How do I tell whether a replication source server is using statement-based or row-based binary logging format? A.14.11. How do I tell a replica to use row-based replication? A.14.12. Note that if your replica has been disconnected from the source ...
https://dev.mysql.com/doc/refman/8.0/en/fulltext-search.html
For large data sets, it is much faster to load your data into a table that has no FULLTEXT index and then create the index after that, than to load data into a table that has an existing FULLTEXT index. This rules out, for example, a table column ...