1994.5.36
by Stewart Smith
add some FIXME to analyze docs. |
1 |
ANALYZE
|
1887.3.2
by Brian Aker
Extended documentation. |
2 |
=======
|
3 |
||
2194.5.2
by Andrew Hutchings
Fix SQL markup |
4 |
Syntax: |
5 |
||
6 |
.. code-block:: mysql |
|
1994.4.83
by Marisa Plumb
table update functions edits, starting authentication |
7 |
|
1994.4.114
by Marisa Plumb
markup fix |
8 |
ANALYZE [LOCAL | NO_WRITE_TO_BINLOG] TABLE tbl_name [, tbl_name] |
1994.4.83
by Marisa Plumb
table update functions edits, starting authentication |
9 |
|
2222.2.1
by Mark Atwood
documentation work |
10 |
ANALYZE TABLE usually read locks a table, and then analyzes and stores |
11 |
the key distribution for a table. |
|
1994.4.83
by Marisa Plumb
table update functions edits, starting authentication |
12 |
|
13 |
ANALYZE functionality differs depending on the storage engine. |
|
14 |
||
2222.2.1
by Mark Atwood
documentation work |
15 |
On InnoDB tables, using ANALYZE will result in a WRITE LOCK on the |
16 |
table. It also will not perform an explicit gathering of statistics |
|
17 |
when you issue an ANALYZE command. To update the index cardinality, |
|
18 |
there will be 10 random dives into each index, retrieving an estimated |
|
19 |
cardinality. Therefore, several ANALYZE TABLEs in a row are likely to |
|
20 |
produce different results each time. |
|
1994.4.83
by Marisa Plumb
table update functions edits, starting authentication |
21 |
|
2222.2.1
by Mark Atwood
documentation work |
22 |
Statistics-gathering with ANALYZE has recently been added to HailDB so |
23 |
that index dives are performed. |