Starting with MySQL 8.0, we will drop libmysqld (aka “embedded server”). This change will affect only a handful of users, but for context let me start with an introduction.
Introduction
libmysqld (also referred to as “the embedded server”) is a way of using MySQL without the client server protocol.…
Does InnoDB page size matter? janlindstrom Wed, 10/26/2016 - 23:44
From MariaDB 10.1 there is a feature where the InnoDB page size can be configured to be larger than the default 16K for normal, uncompressed tables. However, there has been little performance results that show whether the page size really effects the transaction performance or response time. In this blog, we study effects of page size on three different storage devices using the same benchmark(s). These devices are:
Results from different devices should not be compared to each other, as there are other variables like device bandwidth and different file systems. Instead, we will look at page …
[Read more]In previous blog posts we explained how to perform certain actions in a MySQL database set up as a document store using Connector/Node.js. In this blog post we are going to use some of the examples covered to explain how to start working with an application created with Express.js, AngularJS, Node.js, and MySQL Connector/Node.js.
Required
Optional
A quick look at ProxySQL
There is a lot of buzz in the MySQL community around ProxySQL, an open-source SQL-aware proxy. I was lucky enough to give a ProxySQL Tutorial at PerconaLive Amsterdam 2016 with the creator of ProxySQL, René Cannaò.
Some of ProxySQL’s features include:
ProxySQL’s approach to implementing regex-style query rules opens the door to some pretty fascinating possibilities. Just to name a few examples:
Dear MySQL users,
MySQL Connector/Python 2.0.5 GA is a new GA version of 2.0 release series of the pure Python database driver for MySQL. It can be used for production environments.
MySQL Connector/Python version 2.0.5 is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported.
MySQL Connector/Python 2.0.5 is available for download
from:
http://dev.mysql.com/downloads/connector/python/#downloads
The ChangeLog file included in the distribution contains a brief
summary of changes in MySQL Connector/Python 2.0.5. For a more
complete list of changes, see below or online at:
http://dev.mysql.com/doc/relnotes/connector-python/en/
Changes in MySQL Connector/Python 2.0.5 (2016-10-26)
Bugs Fixed
* A potential SQL injection vector was eliminated. (Bug #22529828, …
[Read more]
In our current project the customer wants to install and run
multiple MySQL Enterprise Server 5.7 Instances on the same
machine (yes, I know about virtualization (we run on kvm),
containers, Docker, etc.). He wants to use Red Hat Enterprise
Linux (RHEL) 7 which brings the additional challenge of SystemD.
So mysqld_multi is NOT an option any more.
We studied the MySQL documentation about the topic: Configuring Multiple MySQL Instances Using systemd. But to be honest: It was not really clear to me how to do the job...
So we started to work out our own cook-book which I want to share here.
The requirements are as follows:
Take Percona’s poll on what database technologies you use in your environment.
Different databases get designed for different scenarios. Using one database technology for every situation doesn’t make sense, and can lead to non-optimal solutions for common issues. Big data and IoT applications, high availability, secure backups, security, cloud vs. on-premises deployment: each have a set of requirements that might need a special technology. Relational, document-based, key-value, graphical, column family – there are many options for many problems. More and more, database environments combine more than one solution to address the various needs of an enterprise or application (known as polyglot persistence).
Please take a few seconds and answer the following poll on database technologies. Which are you using? Help …
[Read more]This release introduces a new major feature – GUI transaction support – as well as some minor features and bug fixes.
Changes as compared to MySQL GUI 12.2.6 include:
Features:
* GUI transactions support. This new feature is available in
Enterprise and Ultimate editions. Also please see note
below.
* Added a tooltip on column headers in Data tab informing
about column name, column type and length.
In Result tab the tooltip will display column name only, as
the result returned by MySQL does not have information of
storage type details.
* Added GUI support for index-level comments in CREATE/ALTER
TABLE.
Bug Fixes:
* Fixed an issue where GUI could ‘hang’ when executing queries
with very large subqueries.
* Fixed an issue with the …
Working as MySQL DBA, you will often have to deal with schema changes. Changes to production databases are not popular among DBAs, but they are necessary when applications add new requirements on the databases. If you manage a Galera Cluster, this is even more challenging than usual - the default method of doing schema changes (Total Order Isolation) locks the whole cluster for the duration of the alter. There are two more ways to go, though - online schema change and Rolling Schema Upgrade.
A popular method of performing schema changes, using pt-online-schema-change, has its own limitations. It can be tricky if your workload consists of long running transactions, or the workload is highly concurrent and the …
[Read more]
Setting the correct total maximum connections of your server
depends on how large your memory is. Each connection thread
consumes an amount of your total memory. For example you have 4GB
memory in your server and each thread is using around 2MB of RAM,
a 100 concurrent connections is actually eating up a total of
200MB of your memory.
So how do we compute the max_connections?
1. First is you need to do is get the value of the following
global variables. Examine and take note of their sizes. The value
stored in the database is actually in bytes so you might need to
convert it to Kilobytes or Megabyte or Gigabytes by dividing it
to 1024
Example:
1,073,741,824 bytes
1,073,741,824 / 1024 = 1,048,576 kilobytes
1,073,741,824 /1024 / 1024 = 1,024 megabytes
1,073,741,824 / 1024 / 1024 / 1024 = 1
gigabytes
You can use the SHOW command to display …
