… e.g. alter table foo disable query_cache; create table bar (id int(4) auto_increment, value varchar(255)) disable query_cache; Not that…
Comment: Should we give a MySQL Query Cache a second chance ?
April 10, 2011 By 64 Comments
… e.g. alter table foo disable query_cache; create table bar (id int(4) auto_increment, value varchar(255)) disable query_cache; Not that…
Post: SSD, XFS, LVM, fsync, write cache, barrier and lost transactions
March 2, 2009 By 32 Comments
… very primitive test with INSERT INTO fs VALUES(0) into auto-increment field into InnoDB table. InnoDB parameters are innodb_buffer_pool… in conclusion to warranty Durability with SSD we have to disable write-cache which can affect performance results significantly (I have… in default mode 2. To have durability we need to disable write cache ( with following performance penalty, how much we need…
Post: Performance gotcha of MySQL memory tables
February 1, 2008 By 5 Comments
… test table: CREATE TABLE `test` ( `id` int(11) NOT NULL auto_increment, `c` tinyint(4) default NULL, PRIMARY KEY (`id`), KEY `c… per second for Innodb (with log flush at transaction commit disabled) The results might sound to be to bad to be… Buffer Pool and log flush on transaction commit was also disabled, meaning Innodb could delay writes and do all the changes…
Post: Is there room for more MySQL IO Optimization?
January 3, 2013 By 11 Comments
… Max_data_length: 0 Index_length: 9047113728 Data_free: 6291456 Auto_increment: NULL Create_time: 2012-12-31 16:24:54 Update… MySQL 5.6) so I tried that as well as disabling read ahead all together. In both cases for this given…
Post: How to STOP SLAVE on Amazon RDS read replica
December 20, 2012 By 4 Comments
… DATABASE percona; master> CREATE TABLE percona.test (id int unsigned auto_increment not null primary key); replica> INSERT INTO percona.test VALUES… course, for that to work, you will also have to disable read_only mode, which you can do by going to…
Comment: Why audit logging with triggers in MySQL is bad for replication
September 29, 2008 By 10 Comments
… this is to find a way not to have an auto-incremented key on the history table. If you can make a… do either of those, then I would suggest that you disable the crc check on this table and just have mk…
Comment: MySQL Installation and upgrade scripts.
May 21, 2007 By 3 Comments
….0.27 – slow, with “check for upgrade” repairs, problems with auto_increment values in the replication binlogs (bug #24432) 5.0.36sp1… to blindly migrate to. — Oh, yes, SELinux had to be disabled. At the present time I decided to upgrade to 5…
Post: MySQL 5.5 and MySQL 5.6 default variable values differences
February 21, 2013 By 8 Comments
…_limit is 5000 by default now vs 1024. innodb_auto_extend_increment is now 64MB instead of 8MB which should help to… to create Innodb table but getting MyISAM because Innodb was disabled for some reason was very error prone gotcha. Note this… any practical meaning for users. Considering the default innodb_auto_extend_increment is 64 starting with 64M might have made more sense…
Post: Percona XtraBackup 1.6
April 12, 2011 By 15 Comments
… passed directly to the xtrabackup script and –incremental-basedir is ignored. (Vadim Tkachenko) Added option –incremental-dir to innobackupex. This option is… for XtraBackup. (Aleksandr Kuzminsky) Disabled auto-creating ib_logfile* when innobackupex is called with –redo-only or with –incremental-dir. If neccessary ib…
