|Showing entries 1 to 30 of 30|
Seeing as it looks like 5.5 is shortly about to go GA I thought I’d give it a run and see how well it works. The only way really to test it is to give it a bit of load and look for things which break. That I did with the 5.5.6-rc community rpms, compared to the 5.1 advanced rpms I usually run.
My colleagues, Ben and Peter, found a horrible problem which means that I can’t use this even for any real usage on my real servers. See: bug#57095 for all the gory details. Thanks to them both for finding the problem and then digging down and figuring out the real cause. Sometimes developers work a long way from the database so their errors don’t translate into something I can really look at in the database. They delved into the problem and then found the cause and a nice easy test[Read more...]
Recently while we were building a slave with a newer version of MySQL 5.1 from an InnoDB Hot backup, the following error occurred when we ran
mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Running 'mysql_fix_privilege_tables'... ERROR 13 (HY000) at line 311: Can't get stat of './mysql/general_log.CSV' (Errcode: 2) ERROR 13 (HY000) at line 316: Can't get stat of './mysql/slow_log.CSV' (Errcode: 2) FATAL ERROR: Upgrade failed
The problem is that in MySQL 5.1, it is possible to log the slow query log and general log to tables in the
There seems to be an optimizer problem in 5.1, if you put a NULL in the IN clause of a SELECT. For example, given the following table:
CREATE TABLE foo ( a INT NOT NULL AUTO_INCREMENT, PRIMARY KEY (a) );
Compare these two EXPLAINs:
mysql> EXPLAIN * FROM foo WHERE a IN (160000, 160001, 160002)\G *************************** 1. row *************************** id: 1 select_type: SIMPLE table: foo type: range possible_keys: PRIMARY key: PRIMARY key_len: 4 ref: NULL rows: 3 Extra: Using where 1 row in set (0.06 sec) mysql> EXPLAIN SELECT * FROM foo WHERE a IN (NULL, 160000, 160001, 160002)\G *************************** 1. row *************************** id: 1 select_type: SIMPLE table: foo type: ALL possible_keys: PRIMARY key: NULL[Read more...]
Look what arrived in the mail! MySQL 5.1 Release t-shirts!
We made something similar for the MySQL 5.0 release and 10th anniversary, and sold that. I don’t know if we have plans to sell the MySQL 5.1 t-shirts, but if you think you’d like to buy one, maybe drop me a comment and if there’s enough requests for it, I’m sure we’ll try to sort something out.[Read more...]
With the release of MySQL 5.1, many DBAs are going to be scheduling downtime to upgrade their MySQL Server. As with all upgrades between major version numbers, it requires one of two upgrade paths:
I’m here to present a third option. It requires minimal application downtime, and is reasonably simple to prepare for and perform.
First of all, you’re going to need a second server (which I’ll refer to as S2). It will act as a ’stand-in’, while the main server (which I’ll refer to as S1) is upgraded. Once S2 is ready to go, you can[Read more...]
There’s a change of behaviour in MySQL 5.1.31 for Row Based Replication, if you have InnoDB transactions that also write to a MyISAM (or other non-transactional engine) table. It’s a side effect of fixing Bug #40116. Take this simple example:
Transaction 1: INSERT INTO myisam_tbl (item, val) VALUES (1, 0); Transaction 1: INSERT INTO innodb_tbl (item, val) VALUES (1, -1), (2, -1); Transaction 1: START TRANSACTION; Transaction 1: UPDATE myisam_tbl SET val=val+1 WHERE item=1; Transaction 1: UPDATE innodb_tbl SET val=( SELECT val FROM myisam_tbl WHERE item=1 ) WHERE item=1; Transaction 2: START TRANSACTION; Transaction 2: UPDATE myisam_tbl SET val=val+1 WHERE item=1; Transaction 2: UPDATE innodb_tbl SET val=( SELECT val FROM myisam_tbl WHERE item=1 ) WHERE[Read more...]
Do you remember Guy Adams? He was one of the winners of the “5.1 Use Case Competition”, ending up on position #2. Guess what: He has a webinar coming up tomorrow, by the title Deploying MySQL in a High Performance Satellite Network Management Environment by Parallel.
Guy works with Parallel Ltd. in Milton Keynes in the UK. You may also want to read up on
According to Vadim at Percona:
It's 100% backwards-compatible with standard InnoDB, so you can use it as a drop-in replacement in your current environment. It is designed to scale better on modern hardware, and includes a variety of other features useful in high performance environments.
The release is pure GPL (v2) and commercial support is available from Percona. If percona keeps this up, they just might become the new MySQL.
The source[Read more...]
I suspect that few of the readers of my blog have missed it, but MySQL 5.1 is GA (http://www.mysql.com/products/enterprise/server.html" target="_blank). And I suspect it was no surprise to my readers, nor those of Giuseppe, the Community Team Lead. Nor those who read Sheeri’s blog, with the picture of Dups unmistakably setting GA date expectations at the OpenSQL Camp a number of weeks ago.[Read more...]
When Monty Widenius published his criticisms of MySQL 5.1 recently a lot of the coverage that followed focused on his belief that the product had been made generally available too early and has too many serious bugs.
A solution to this problem would have been told hold 5.1 back even longer for more testing or, better still, not to have announced it as a release candidate so early. However, reading Monty’s post in full indicates that this would be a matter of treating the symptoms rather than finding a cure.
He also wrote: “the MySQL current development model doesn’t in practice allow the MySQL community to participate in the development of the MySQL server” and “I think it’s time to seriously review how the MySQL server is being developed and[Read more...]
First, initially we will deliver both MySQL Enterprise Server and MySQL Community Server in parallel. The bug fixes to the initial MySQL 5.1 GA releases will thus be delivered also in binary form for both MySQL Community Server and MySQL Enterprise Server.
Second, after a period of time, we will revert to the different release schedule for MySQL Enterprise Server and MySQL Community Server that we have been using. MySQL Enterprise Server will have more frequent binary releases. However, at this point, we do not have[Read more...]
Thanks and congratulations,[Read more...]
The GA announcement of MySQL 5.1 is coming, and for downloading, it’s already available, as I hope you have noticed from Giuseppe’s blog. We continue our preparations, this time by announcing Position 2 in the MySQL 5.1 Use Case Competition.
2. Guy Adams (Parallel Ltd., Milton Keynes, United Kingdom): Using Partitioning to Manage Satellite Networks. See Guy’s DevZone article.[Read more...]
The GA announcement of MySQL 5.1 is getting closer by the minute! So it’s time for Position 3 in the MySQL 5.1 Use Case Competition.
Thanks and congratulations, Corrado! I hope you are in a position to take[Read more...]
4. Volker Oboda (TeamDrive Systems GmbH, Hamburg, Germany): Using the Pluggable API for TeamDrive. See Volker’s DevZone article, and[Read more...]
To keep you in suspense, let me first announce those on positions 5 to 10:
5. Fourat Zouari (TriTUX.com, Tunis, Tunisia): Using Partitioning for Data Warehousing. See Fourat’s DevZone article, and[Read more...]
Reading this article you will learn how to create a Customized Performance Report for one of your MySQL™ Servers using HoneyMonitor, a GUI for MySQL™ Server Administration, Monitoring & Performance Tuning.
This is my Report for the MySQL™ 5.1 Use Case Competition.
Before start reporting on my use of the new 5.1 Features, just a note.
I was quite sure on early August 2008 that including similar posts in my Report would be allowed. But during an[Read more...]
|Showing entries 1 to 30 of 30|