Thank you Aaron! The first query is quite a find! Note that I just barely recognized the blog name from your profile on DBA.SE, though this post I found via Googling for MySQL indexes.
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* New …
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* New feature: Compressed .sql file export
* Migration to the brand new Delphi XE …
This is the first release which ships a 64 bit version along with
the 32 bit one. The installer includes both versions. Installing
over an existing 32 bit instance will again install the 32 bit
version. So if you prefer 64 bit you will need to uninstall
first.
Get it from the download page.
Here are the most noticable changes and new features:
* 64 bit version allows HeidiSQL to use much more of your
memory than the 2GB in 32 bit mode
* New feature: Fast table status for databases with InnoDB
tables. (Disable Session > Advanced > [X] Get full
table status)
* New feature: Favorites in database tree
* New feature: Append parameter names for procedures and
functions in completion proposal
* …
So how do you get MySQL 5.5, 5.6, or 5.7 on the latest Oracle Linux? Morgan had a great post on Installing MySQL 5.7 DMR3 with the official yum repos. This blog is about uprading from Oracle Linux 6.4 to 6.5 and getting a recent version of MySQL installed.
The first step, if you are running Oracle Linux 6.4, is to type yum install to upgrade to 6.5. Be sure to read the release notes and that you are pointing to the Public Yum Repository.
Use can use the Add/Remove Software tool to install MySQL 5.1. But who wants to run an old version of MySQL on a new, hot Linux. But let’s pretend you did install 5.1 when you installed 6.4 and now you are all sixes and sevens. So what do you do?
…
[Read more]I clicked around for a few moments but didn’t immediately see a license mentioned for the MariaDB knowledgebase. As far as I know, the MySQL documentation is not licensed in a way that would allow copying or derivative works, but at least some of the MariaDB Knowledge Base seems to be pretty similar to the corresponding MySQL documentation. See for example LOAD DATA LOCAL INFILE: MariaDB, MySQL.
Oracle’s MySQL documentation has a licensing notice that states:
You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or …
[Read more]
At Facebook, we have upgraded most of MySQL database tiers
to 5.6, except very few tiers that have a special requirement --
very fast single threaded replication speed.
As Oli mentioned, single threaded performance is
worse in 5.6. The regression is actually not visible in most
cases. For remote clients, the performance regression is almost
negligible because network latency is longer than 5.1->5.6
overhead. If clients are running locally but MySQL server is disk
i/o bound, the overhead is negligible too because disk i/o
latency is much longer than 5.1->5.6 overhead.
But the regression is obvious when clients run locally and
queries are CPU bound. The most well known local client program
for MySQL is SQL Thread (Replication Thread). Yes, 5.6 has a
slower replication performance problem, if SQL thread is …
On Tuesday 17th December, we’ll be presenting a webinar on the
latest developments for MySQL Fabric (a framework for managing
pools of MySQL server – together with 2 applications: automated
sharding and High Availablity). As always, the webinar is free
and you should register here.
This is your opportunity to hear the details directly from the engineering team and put your questions to them.
This session will present MySQL Fabric and help you understand how you will be able to leverage it to address your scaling needs:
- Architecture for performance of a sharded deployment
- Management of MySQL server farms via MySQL Fabric
- MySQL Fabric as a tool for …
In the MySQL team @ Oracle, we’ve been discussing changing the default values for MySQL replication so that they are safer to use.
Specifically:
| Setting | Current Value | Proposed New Value |
| sync_binlog | 0 | 1 |
| master-info-repository | FILE | TABLE |
| … |
In my last post, a tale of two MySQL upgrades, a few folks asked if I would outline the process we used to upgrade, and what kind of downtime we had.
Well, the processes were different for each upgrade, so I will tackle them in separate blog posts. The first step was to upgrade all our MySQL 5.1 machines to MariaDB 5.5. As mentioned in the previous post, MariaDBs superior performance for subqueries is why we switched and we switched back to MySQL for 5.6 to take full advantage of the performance_schema.
It is not difficult to blog about our procedure, as we have documentation on each process. My first tip would be to do that in your own environment. This also enables other folks to help, even if they are sysadmins and not normally DBAs. You may notice the steps contain items that might be obvious to someone who has done maintenance before we try to …
[Read more]