This week we continue our interview with Noam Kritzer of Bakos & Kritzer, talking about patent case law and patent trolls. Ear Candy is temporary table ghost files, and At the Movies is Manipulating JSON with MariaDB and MySQL.
defensive vs. offensive patents
Copyright.gov, a resource written for lay people.
We know very well that database technologies need a blog presence, and how to best offer that blogging experience — without the danger of boredom — is something tons of Oracle, SQL Server, and MySQL bloggers continue to show through Log Buffer. Enjoy!
Oracle:
Various approaches exist to organize your groovy scripts and package up utilities.
Oracle Certification announces the release of the new Oracle Linux 6 certification paths.
Designed for the Cloud, the new multitenant architecture of Oracle Database 12c now enables customers to greatly simplify and accelerate database consolidation by …
[Read more]Percona is glad to announce the release of Percona XtraBackup 2.1.4 on August 9th, 2013. Downloads are available from our download site here and Percona Software Repositories.
This release is the current GA (Generally Available) stable release in the 2.1 series. Percona XtraBackup is an open source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases.
New Features:
Recently i updated to MySQL 5.6 and we were really excited about the very good overall performance. But beside a major bug concerning wrong results when running a SELECT that includes a HAVING based on a function (see http://bugs.mysql.com/bug.php?id=69638) we also noticed that from time to time the replication breaks with the following error:
Last_SQL_Errno: 1590 Last_SQL_Error: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log
After some investigation it seemed like this happens if one modifies some user privileges, so we stumbled upon http://bugs.mysql.com/bug.php?id=68892.
Essentially the bug report says that if you use the wrong syntax for GRANT-statements the replication will break. So far, so bad. I told everyone who had the …
[Read more]
I have rehashed a list of useful reporting queries from my blog
which I hope people would find useful for their business or
clients. These are not MySQL specific, by any means.
Orders
Products (Best Sellers)
I’m happy to announce that the recording for my recent webinar “5 Proactive Measures to Minimize MySQL Downtime” is now available, along with the slides. They can both be found here.
My webinar focused on the top 5 operational measures that prevent or reduce downtime — along with the related business impact in a significant number of customer emergency scenarios.
As a senior consultant on Percona’s 24×7 Emergency Consulting team, I’ve helped resolve a …
[Read more]Looking at the committers/authors of patches in the bzr tree for MariaDB 5.5.31.
Non Oracle Contributors:
Oracle (as they pull Oracle changes):
I grabbed all the tests introduced in MariaDB 5.5.32 (i.e. “bzr diff -rtag:mariadb-5.5.31..mariadb-5.5.32 mysql-test/” and some foo) and threw them in their own test file. I only kept tests for crashing bugs and ignored those that required plugins (there were two or three, but nothing major). So now I have a test file that should crash MariaDB 5.5.31 and probably before. But, the question is: does this crash Percona Server or MySQL?
While it is excellent to see the MariaDB guys including tests for their crashing bugs, are these MariaDB specific or do they affect other MySQL flavours?
I built a release build of top of trunk Percona Server and ran the test against it. I got no crashes. In a debug build, I got two. One was to do with REPAIR on an ARCHIVE table and the other was “SELECT UNIX_TIMESTAMP(STR_TO_DATE(’2020′,’%Y’));”. I found the same thing for a debug build of top of tree MySQL.
All the other tests …
[Read more]To only slightly misquote one of the greatest movies of all times:
You keep using that option. I do not think it means what you think it means.
Perhaps like many users, I had certain assumptions about what max_connect_errors really does – but in looking closely as part of investigating the new PERFORMANCE_SCHEMA.HOST_CACHE table in MySQL 5.6, I learned that some very fundamental elements had escaped my notice. I’m writing this blog post to help others who hold similar misconceptions of what this option does.
Many, if not most, MySQL DBAs are familiar with “host blocked” errors:
C:\mysql-5.5.27-winx64>bin\mysql -utest_mce -P3307 -h192.168.2.8 ERROR 1129 (HY000): Host …[Read more]
The much-improved PERFORMANCE_SCHEMA in MySQL 5.6 provides visibility into MySQL’s host cache, including the ability to monitor for impending blocked hosts. You can do this with the following query:
mysql> SELECT
-> ip,
-> host,
-> host_validated,
-> sum_connect_errors
-> FROM performance_schema.host_cache\G
*************************** 1. row ***************************
ip: 192.168.2.4
host: TFARMER-MYSQL.wh.oracle.com
host_validated: YES
sum_connect_errors: 3
1 row in set (0.02 sec)
That’s helpful information, and allows DBAs to identify problematic hosts before they are blocked. Due to Bug#69807, it’s also something MySQL 5.6 users will want to do. This bug causes the counter maintained in the host …
[Read more]