May 25, 2012

Post: A recovery trivia or how to recover from a lost ibdata1 file

…switching to Innodbmysql -u root -e “alter table recover.$CURRENT_TABLENAME engine=Innodb;” sleep 1 echo “discarding tablespace ” mysql -u root -e “alter table recover…the recovery completed. The customer was able to download the tables in MyISAM format and then he just convert them back to InnoDB

Post: Pitfalls of converting to InnoDB

… recommend to our clients to convert their current database from MyISAM tables to InnoDB. The transfer by itself in most cases is … tables” $DBNAME); do echo “Converting table $t” mysql -u$DBUSER -p$DBPWD -e “alter table $t type=InnoDB” $DBNAME; done There is the standard script mysql_convert_table

Post: How Percona does a MySQL Performance Audit

tables, I’ll paste in mysql> show global variables like ‘%table_size%’; +———————+———–+ | Variable_name | Value | +———————+———–+ | max_heap_table_size | 268435456 | | tmp_tableto convert MyISAM tables to InnoDB

Post: Percona Server 5.5.11-20.2 Stable Release

… equivalent, ‘innodb_rollback_segments’, has been implemented in MySQL 5.5. (Yasufumi Kinoshita) Bug Fixes Bug #757749 – Using ALTER TABLE to convert an InnoDB table to a MEMORY table could fail due to a bug in innodb_expand…

Post: Percona Server 5.1.58-12.9

INNODB_SYS_TABLES after an ALTER TABLE statement leaded to a server crash. Bug Fixed: #627189 (Yasufumi Kinoshita). The 64-bit CAS implementation may lead to

Comment: Pitfalls of converting to InnoDB

Here is a quick shell script to convert all tables in a database to InnoDB. No dependancies other than a command line prompt on a Un*x like system and the standard MySQL tools: for T in `mysql -u root -B -N -e “show tables” test`; do mysql -u root -e “alter table $T type=innodb” test…

Comment: MySQL Server Memory Usage

… cannot really convert the gained knowledge to solve …’76′ ‘Com_alter_db’, ’0′ ‘Com_alter_table‘, ’7′ ‘Com_analyze’, ’0′ ‘Com_backup_table‘, ’0′…mysql innodb_table_locks=0 innodb_buffer_pool_size=1800M # USE ALL MEMORY AVAILABLE #innodb_log_buffer_size=8M # Lowered from 32M according to MySQL innodb

Post: Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs

mysql> drop table salaries; — Ooops! Query OK, 0 rows affected (0.49 sec) mysql> alter table

Comment: Database problems in MySQL/PHP Applications

Innodb tables do internal full tableMySQL. Good design will help dictate how many tables are required in order to get the job done. ToALTER TABLE or OPTIMIZE TABLE > now locks small table for few seconds rather than giant 100GB tableconverting your varchars to chars for example), then having to

Post: Estimating Undo Space needed for LVM Snapshot

to 2 writes, however similar to Innodb DoubleWrite the overhead is not double – the blocks written toto do maintainence or batch job, which well may require a lot of undo space. Running ALTER TABLE or OPTIMIZE TABLE will cause table