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/innodb-compression-tuning.html
The compressed page size should always be bigger than the maximum record size, or operations may fail as noted in Compression of B-Tree Pages. If the compressed page size is set too small, inserts or updates may require time-consuming recompression, ... Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed ...
https://dev.mysql.com/doc/refman/8.0/en/descending-indexes.html
MySQL supports descending indexes: DESC in an index definition is no longer ignored but causes storage of key values in descending order. Previously, indexes could be scanned in reverse order but at a performance penalty. A descending index can be ...
https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
A value of 6 is considered drastic because database pages are left in an obsolete state, which in turn may introduce more corruption into B-trees and other database structures. Leaves database pages in an obsolete state, which in turn may introduce ... To investigate database page corruption, you might dump your tables from the database with SELECT ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html
These clauses are primarily useful when dealing with tree-structured or graph-structured data, either in a single table or split across multiple tables. You traverse edges or tree branches from one place to another, while reserving the right to come ... If you query data and then insert or update related data within the same transaction, the regular SELECT statement does not give enough ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/8.0/en/features.html
This section describes some of the important characteristics of the MySQL Database Software. In most respects, the roadmap applies to all versions of MySQL. Tested with Purify (a commercial memory leakage detector) as well as with Valgrind, a GPL ...
https://dev.mysql.com/doc/refman/8.0/en/getting-mysql.html
To obtain the latest development source, see Section 2.8.5, “Installing MySQL Using a Development Source Tree”. Check our downloads page at https://dev.mysql.com/downloads/ for information about the current version of MySQL and for downloading ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-spatial-analysis.html
The most typical operations are: Point queries that search for all objects that contain a given point Region queries that search for all objects that overlap a given region MySQL uses R-Trees with quadratic splitting for SPATIAL indexes on spatial ... For MyISAM and InnoDB tables, search operations in columns containing spatial data can be optimized using SPATIAL ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-instrument-naming.html
Example names: wait/io/file/myisam/log wait/io/file/mysys/charset wait/lock/table/sql/handler wait/synch/cond/mysys/COND_alarm wait/synch/cond/sql/BINLOG::update_cond wait/synch/mutex/mysys/BITMAP_mutex wait/synch/mutex/sql/LOCK_delete ... An ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-optimization.html
For additional information about hash indexes, see Section 10.3.9, “Comparison of B-Tree and Hash Indexes”. Applications that monitor databases may make frequent use of Performance Schema tables. To write queries for these tables most ...