May 23, 2012

Post: MySQL Installation and upgrade scripts.

to the new major version make sure you upgrade to latest current version at first. Ie upgrade to recent MySQL 5.0 before upgrading to MySQL 5.1to write not about MySQLlogged some of my experiences as a bug but here are some more details about the problems Upgrade Script fails to shut down MySQL

Post: How Percona does a MySQL Performance Audit

… Linux Server release 5.2 (Tikanga) …log-error=/var/log/mysqld.log mysql 3172 3137 78 Nov19 ? 1…if the query fails, then you…to use a patched binary, we can use MySQL Proxy, packet sniffing, or other techniques to get more information than the slow log…you need to really know how to write queries…

Post: ORDER BY ... LIMIT Performance Optimization

… web sites failing to take care of this provides very easy task to launch a …slow query log as query which does not use indexes, even if it is quite fast: mysql1.6 million of rows to be scanned, while we well know it will be just 5… are some differences. I should write another article about ORDER BY …

Post: Multiple purge threads in Percona Server 5.1.56 and MySQL 5.6.2

to get rid of–purge–the old versions of the records as they become obsolete. In MySQL 5.1log_file_size=1900M innodb_flush_log_at_trx_commit=2 innodb_doublewrite=1writing, the code is already different in the trunk. Huh? The dedicated purge threads in 5.6.2 completely fail to…they only slow the growth…

Post: SHOW INNODB STATUS walk through

MySQL 5LOGLog sequence number 84 3000620880 Log flushed up to 84 3000611265 Last checkpoint at 84 2939889199 0 pending log writes, 0 pending chkp writes 14073669 log

Post: Updated msl (microslow) patch, installation walk-through!

mysql-5.0.51a) % su root Password: First you should apply the changes to the database configuration, specifically you need to enable slow logginglogged while doing it only for every n-th of them thus limiting the number of writes to the log. Note: this feature will fail to

Post: Percona Server 5.1.47-rel11.0

slow_query_log option to use microsecond precision for the slow query log‘s timestamps (issue #358412). Added the –use_global_log_slow_control option to control slow-query loggingfails to compile with CFLAGS=-DUNIV_DEBUG #569156 CentOS 5: mysql-server conflicts with MySQL

Comment: Database problems in MySQL/PHP Applications

5 log-slow-queries=/apps/log/slowfails to # connect), the slave will create a master.info file, and any later # change in this file tolog-bin # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname tmpdir =/mysqlwrite

Post: MySQL Crash Recovery

…system extremely slow and …to use innodb-safe-binlog option in MySQL 4.1 so your Innodb log and binary log are synchronized. In MySQL 5MySQL to fail with wierd error messages. In MySQL 4.1to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb tablespace recovery etc but I should write