June 19, 2013

Post: Neat tricks for the MySQL command-line pager

… own, that’s not really a limitation.(Edit: I’m wrong! You can. See …1 ‘TRX HAS BEEN WAITING’ Now in your mysql session, set /tmp/lock_waits as …Bookmark lookup | +- Table | | table actor | | possible_keys PRIMARY | +- Unique index lookup | key actor->PRIMARY | possible_keys PRIMARY | key_len 2 | ref …

Post: MySQL 6.0 vs 5.1 in TPC-H queries

possible_keys | key | key_len | ref | rows | Extra | +—-+————-+———-+——-+—————+—————+———+——+———+———————————————–+ | 1 | SIMPLE | lineitem | range | li_shp_dt_idx | li_shp_dt_idx | 3 | NULL | 8272067 | Using index

Post: Beware of MySQL Data Truncation

mysql> explain select count(*) from article_comment where article_id=4300000000; +—-+————-+—————–+——+—————+————+———+——-+——+————————–+ | id | select_type | table | type | possible_keys | key | key

Post: Why MySQL could be slow with large tables ?

not different selectivity might show benefit from using indexes. In fact even MySQL optimizer currently does not take it into account. For In memory workload indexwrong. Do not take me as going against normalization or joins. It is great principle and should be used when possible. Just do not

Post: MySQL Crash Recovery

…and do not expose itself instantly – you may notice wrong query … as possible. This hack is needed only in some cases – innot be basing my failure handling scenarios. Cold Start – If you restart MySQL server its caches (key…- Unlike MyISAM Innodb does not store index cardinality in tables, instead it…

Post: Why you should ignore MySQL's key cache hit ratio

MySQL‘s key cache hit ratio is wrong, even when you hear it from experts. There are two major problems with the keypossibility of having multiple key caches. But I’ll give the simple version here. In my opinion, you should choose a key

Post: How adding another table to JOIN can improve performance ?

possible_keys: d key: d key_len: 7 ref: NULL rows: 3681 Extra: Using where 1 row in set (0.01 sec) mysql

Post: Heikki Tuuri Innodb answers - Part I

not serializable. PZ: Cool. This is one of little known new features in MySQLin 5.1.x? Is it possiblekey and the referenced key appear as the FIRST (leftmost) columns in an index, in the same order in the foreign key and the referenced key

Comment: Database problems in MySQL/PHP Applications

wrong it > is frequently told by people with traditional database background. > Things are different with MySQLIndexes This item was not inpossibilities. Also, indexing the full width of very wide columns will take up tremendous amounts of memory and disk. Because indexes

Post: Merge Tables Gotcha

possible_keys: PRIMARY key: PRIMARY key_len: 4 ref: const rows: 1 Extra: Using index 1 row in set (0.00 sec) Inkey in MySQL manual Here is what it says: Note that the a column is indexed as a PRIMARY KEY in the underlying MyISAM tables, but not in