May 25, 2012

Post: Troubleshooting MySQL Memory Usage

MySQL to identify potential causes. Is it working with large blobs ? Using user variables ? Prepared Statements ? memory tables ? In a lot of cases you have tocomplicated as good tools to detect memory leaks like valgrind are too slow to run in production. So the best thing to

Post: 7 Reasons why MySQL Quality will never be the same

of users use prepared statements. Bug Reporting and Tracking The MySQLto run MySQL in production. MySQL as it is now works for a lot of applications, in particular because most of them use only small portion of MySQL

Post: INSERT INTO ... SELECT Performance with Innodb tables.

have to wait until statement is completed to make sure it will be executed on the slave in proper order. Gets pretty complicatedto be done outside of MySQL Server) as otherwise the script will fail second time. If you need result to be even closer to one of

Comment: Database problems in MySQL/PHP Applications

one must consider the cost of the benefit versus the value added by having the benefit available. Making a blanket statementMySQL you might be > better of using several queries than doing complicated ones. Of > course you would rather use IN() than do 100 of

Post: Recovery beyond data restore

statements and catching up) The main challenge in such failure is the fact you have many trashed copies to deal with. If you have just one or several small tables corrupted you can reload them. One option is to