… MySQL on profuction server for various debugging needs. Unfortunately you can’t switch it on and off without restarting server until MySQL 5.0. What can you do in MySQL 5.0 and below ? Use Our Patch – With this patch you can get all queries logged as… logs” so logs are reopened and written to the file in question. When you have debug info you can just switch it back…
Post: Enabling/Disabling query log without server restart in MySQL 5.0
September 13, 2007 By 13 Comments
Post: MySQL 4 to MySQL 5 Upgrade performance regressions
June 6, 2007 By 8 Comments
… when upgrading from MySQL 4.0 and 4.1 to MySQL 5.0. By serious I mean several times performance difference not just 5-10% you… get same performance as with MySQL 4.1 Disable Binary Logging This allows to get group commit back but obviously you loose point… should stay on MySQL 4.1 until MySQL has taken it away from you as already happened with MySQL 4.0. MySQL 5.0 can offer substantial…
Post: Upgrading MySQL
January 5, 2010 By 23 Comments
…- Upgrade of MySQL 5.0.30 to 5.0.32 is generally likely to expose less issues than 5.0.30 to 5.0.86. The …the old version in case you need to fail back quickly. This especially makes sense for cloud environments … before upgrading and make sure to keep binary logs for some time, in case you run into …
Post: Configuring MySQL For High Number of Connections per Second
January 6, 2012 By 17 Comments
… any account. When a new connection to MySQL is made, it can go into the back_log, which effectively serves as a queue for new connections on operating system size to allow MySQL to handle spikes. Although MySQL… by Domas]), With MySQL 5.5 default back_log of 50 and 2000 connections created per second it will take just 0.025 seconds to fill…
Post: No more MySQL Crash Safe Replication in 5.0 ?
January 29, 2008 By 7 Comments
… more in MySQL 5.0 Baron has spotted it by incident when we were verifying some of examples for High Performance MySQL book. In the bug Heikki explains the code was probably removed in MySQL 5.0 during XA implementation though the code which prints the data back on recovery was not, so it prints you some log…
Post: MySQL 5.5.8 - in search of stability
January 3, 2011 By 11 Comments
… throughput in MySQL 5.5.8. Let’s see what we can do with them. Article [1]Â also advises that innodb_log_file… with innodb_flush_neighbor_pages=0. Okay, we are back to a stable level. Checkpoint age is also back to 3000MB, and dirty…, 14000MB of log space. And, the Percona Server result is ~2x better than the best result I received with MySQL 5.5.8 (with…
Post: Can MySQL temporary tables be made safe for statement-based replication?
May 26, 2008 By 8 Comments
… says “Some non-transactional changed tables couldn’t be rolled back“, which is interesting.) But does that mean it’s safe… Server_id: 1 End_log_pos: 98 Info: Server ver: 5.0.45-log, Binlog ver: 4 *************************** 2. row *************************** Log_name: mysql-bin.000007 Pos: 98…
Post: Backing up binary log files with mysqlbinlog
January 18, 2012 By 2 Comments
… back them up. Recently in MySQL 5.6, mysqlbinlog got a new feature addition that supports connecting to remote MySQL instances and dumping binary log… +%s` FILESIZE=$(stat -c%s “$LASTFILE”) if [ $FILESIZE -gt 0 ]; then echo “Backing up last binlog” mv $LASTFILE $LASTFILE.orig$TIMESTAMP fi…
Post: Jeremy Cole on MySQL Replication
May 27, 2006 By 12 Comments
… update transactions per second from the single thread without battery backed up cache. If you do it is quite possible Operation… things. Two logs are synced now which requires seeks which make certain disks to flush their cache. Watch out for MySQL 5.0 – if you enabled Binary log with MySQL 5.0 you loose group commit which can dramatically increase…
Post: How InnoDB handles REDO logging
February 3, 2011 By 18 Comments
…0 /* Write log buffer to log about once a second and flush */ innodb_flush_log_at_trx_commit = 1 /* Write log buffer to log… logging and the checkpoint on disk. Vadim touched upon this subject recently in his post MySQL 5.5.8… data. A change may be logged and then later rolled back do to an error or …
