As I wrote earlier, we want the default experience in MySQL 5.7 to be secure by default.  Part of this includes securing connections by automatically creating key material and using TLS for connections where possible.  This may have some significant implications for third-party software – especially products which depend upon capturing, evaluating and/or redirecting client/server traffic at the network level.  This blog post is intended to highlight for developers and users of such products potential issues they may want to consider or address during the pre-GA period for MySQL Server 5.7.

What types of products are dependent upon access to unencrypted protocol data?  Most immediately apparent are proxy-based and network capture-based products.  Proxy-based products typically rely on the same characteristics which can …

After we released pquery to the community, and as we started logging bug reports with pquery testcases, it quickly became clear that pquery binaries with statically compiled-in client libraries would be of great convenience, both for ourselves and for the community.

(If you haven’t heard about pquery yet, read the pquery introduction blog post, come and join the pquery introduction lightning talk at Percona Live (15 April just around 6PM in Hall A), or keep an eye out for some of the upcoming episodes in the …

Hi all, a few months have passed since our first preview release of MySQL Group Replication. Now is the time for the second preview release of MySQL Group Replication, the plugin that brings multi-master update everywhere to MySQL, as described in Hello World post.

Introduced changes User interface changes

After receiving plenty of feedback and continuing to pursue a more integrated look and feel with MySQL, we have given the user interface a facelift. Some of the changes are:

• The plugin has been renamed to group_replication, and as a consequence the plugin’s option names were also renamed to group_replication_*;
• Start/stop command: now the commands are START/STOP GROUP_REPLICATION;
• Performance_schema tables were improved to have better names, fields and relationships. …

In MySQL 5.7.6, we added a new feature called Generated Columns. In the initial work all Generated Columns were materialized, even virtual ones. This not only resulted in unnecessary disk space being used and disk I/O being done, but it also meant that any table alteration required that the full table be rebuilt. In the new MySQL 5.7.7 JSON Lab release, we have resolved all of these issues by implementing new features that not only allow users to create non-materialized virtual …

MySQL 5.7 aims to be the most secure MySQL Server release ever, and that means some significant changes in SSL/TLS.  This post aims to tie together individual enhancements introduced over the span of several Development Milestone Releases (DMRs) into the larger initiative.  In the simplest terms, we hope to have a minimal TLS configuration enabled by default, and for connections to prefer TLS by default.  Let’s dig into the various aspects of this:

Generation of TLS key material

MySQL Server has long supported TLS connections, yet very few deployments are actually configured to leverage this.  This is partly because creation of key material – the certificates and keys needed to establish TLS connections – is a multi-step, extra, manual process.  Basic TLS concepts have to be understood, third-party software …

Prior to MySQL 5.7, the CREATE USER command had a number of limitations:

• No way to set both authentication plugin and password
• No way to disable a user
• No way to define user resource limitations
• No way to set a non-default password expiration policy
• No way to require SSL/x509

All of these things could be done through other means, but typically involved other statements, such as GRANT commands.  Starting with MySQL 5.7.6, these can all be done through a new and improved CREATE USER syntax:

Passwords and authentication plugin

The most important aspect to me, from a security perspective, is the ability to now create user accounts with non-default authentication plugins (like sha256_password) and a non-blank password:

mysql> CREATE USER new@localhost
-> IDENTIFIED WITH sha256_password …

MySQL has provided support for proxy users since version 5.5, but the roles-like capabilities offered have been largely unnoticed until recently.  Part of that has been due to limitations on which types of accounts could leverage proxy user capabilities.  This changes with the release of MySQL Server 5.7.7 (Release Candidate), which includes support for proxy user mapping for the standard mysql_native_password and sha256_password authentication plugins.  This post will introduce the new functionality and explain how to leverage it to emulate certain features …

The MySQL Development team is very happy to announce that MySQL 5.7.7, the first 5.7 Release Candidate (RC1), is now available for download at dev.mysql.com (use the “Development Releases” tab). You can find the full list of changes and bug fixes in the 5.7.7 release notes. Here are some highlights. Enjoy!

SYS Schema

Include SYS Schema in MySQL 5.7 (WL#8159) — This work by Mark Leith integrates the SYS Schema (formerly ps_helper) within the MySQL Server by default. The MySQL SYS schema project has …

Don't miss these MySQL clustering and replication keynotes and sessions next week:

Keynote: What has the cloud done lately for my data? (Robert Hodges, VMware)  Moving Workloads Effectively to Hybrid Cloud Deployments (MC Brown, VMware)  Tutorial: Advanced MySQL replication features roundup (Giuseppe Maxia, VMware) Pivot tables: Analytics in pure SQL (Giuseppe Maxia, VMware) The perils of

(この記事は InnoDB Full-Text: MeCab Parser を Yoshiaki Yamasaki が翻訳したものです)

このブログ記事で紹介した一般的なCJK(中国語、日本語、韓国語)のサポートに加えて、私達はMeCabパーサーも追加しました。MeCabは日本語の形態素解析エンジンで、私達は今 …