… are set:- mysql> show index from follow; +——–+————+———-+————–+————–+———–+————-+———-+——–+——+————+———+ | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null…
Post: Using MyISAM in production
June 17, 2006 By 36 Comments
… into trouble. Just one is enough. Lock priorities. By default MySQL treats updates as higher priority operations. You can use SELECT… flushing dirty index blocks from key_buffer to disk, but it also comes at great danger if MySQL Server crashes or power… storage engine can be even better. Read only data, especially packed with myisampack. This can’t be corrupted or updated and…
Comment: ORDER BY ... LIMIT Performance Optimization
December 29, 2008 By 100 Comments
…MySQL I do: > create table c (id integer auto_increment, a integer, b integer, primary key(… | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null |…
Post: Descending indexing and loose index scan
May 9, 2006 By 6 Comments
… to Innodb tables in general – these are features MySQL should get for all storage engines at some point…. Or some storage engines, such as MyISAM (for packed indexes) may have reverse scan being much slower … index covered query you might rather shorten your key to KEY(A,B) to keep index smaller. The…
Comment: Multiple column index vs multiple indexes
August 25, 2008 By 13 Comments
… bug 29857). mysql> show index from t1000; +——-+————+———-+————–+————-+———–+————-+———-+——–+——+————+———+ | Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null…
