Buy Percona ServicesBuy Now!


 | September 11, 2008 |  Posted In: Insight for DBAs

How would you expect AUTO_INCREMENT to work with MERGE tables ? Assuming INSERT_METHOD=LAST is used I would expect it to work same as in case insertion happens to the last table… which does not seems to be the case. Alternatively I would expect AUTO_INCREMENT to be based off the maximum value across all tables, respecting […]

Read More

Beware of running ANALYZE in Production

 | September 2, 2008 |  Posted In: Insight for DBAs

As you might know ANALYZE TABLE just quickly updates table statistics using index dives, unlike with MyISAM when it scans indexes holding table lock for long period of time. So ANALYZE TABLE should be very fast and non intrusive operation doing just little update on the data. Right ?

Read More

Dangerous command

 | May 20, 2008 |  Posted In: Insight for DBAs

Remembering that I did RENAME DATABASE in MySQL 5.1.21 and found it useful I tried it with 5.1.24 (I was playing with 20GB InnoDB database, so dumping is not fastest way) and all my tries finished with “Syntax error”. So RTMF and documentation says “This statement was added in MySQL 5.1.7 but was found to […]

Read More

MySQL Error Message Nonsenses

 | March 16, 2008 |  Posted In: Insight for DBAs

What MySQL honestly was never good at is giving good helpful error messages. Start with basics for example – The error message in case of syntax error gives you information about tokens near by but little details:

It would be much better if MySQL would give error give exact position of error (with complex […]

Read More

No more MySQL Crash Safe Replication in 5.0 ?

 | January 29, 2008 |  Posted In: Insight for DBAs

As you might know even if you’re only using Innodb tables your replication is not completely crash safe – if Slave MySQL Server crashes/power goes down it is likely for relay logs to run out of sync (they are not synced to the disk) plus position on the master which slave remembers becomes stale. During […]

Read More