Dear MySQL users,
MySQL Connector/ODBC 8.0.19 is a new version in the MySQL
Connector/ODBC
8.0 series, the ODBC driver for the MySQL Server.
The available downloads include both a Unicode driver and an ANSI
driver
based on the same modern codebase. Please select the driver type
you
need based on the type of your application – Unicode or
ANSI.
Server-side prepared statements are enabled by default. It is
suitable
for use with the latest MySQL server version 8.0.
This release of the MySQL ODBC driver is conforming to the ODBC
3.8
specification. It contains implementations of key 3.8
features,
including self-identification as a ODBC 3.8 driver, streaming of
out for
binary types only), and support of the
SQL_ATTR_RESET_CONNECTION
connection attribute (for the Unicode driver only).
The release is now available in source …
MySQL Server 8.0.19, 5.7.29 and 5.6.47, new versions of the popular Open Source Database Management System, have been released. These releases are recommended for use on production systems. For an overview of what’s new, please see http://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html For information on installing the release on new servers, please see the MySQL installation documentation at […]
The MySQL Development team is very happy to announce that MySQL 8.0.19 is now available for download at dev.mysql.com. In addition to bug fixes there are a few new features added in this release. Please download 8.0.19 from dev.mysql.com or from the MySQL Yum, APT, or SUSE repositories.…
Facebook Twitter LinkedIn
MySQL will be in Dubai from JAN13-15.
JAN 13 – 7PM-10PM – MySQL Meetup at Place: Dubai Internet City
Learn more: https://www.meetup.com/MySQL-User-Group-U-A-E/events/267697018/
JAN 14-15 - Oracle Open World - Dubai
- Meet the MySQL team at our dedicated MySQL booth.
- Attend two great MySQL sessions, including a case study with the Digital Solutions’s company Digital 14, which delivers cyber defense and security intelligence solutions with MySQL8.0.
…
[Read more]Queries effect database performance. That’s not a typo: “effect” not “affect”. The difference is not a word game but an important way to think about database performance.
Many things can affect performance. For example, if the system runs out of memory then starts swapping which causes high disk IO latency, that will negatively affect performance. But external factors like that notwithstanding (i.e. when hardware and MySQL are normal and stable), it’s important to understand that queries effect performance.
Queries effect database performance. That’s not a typo: “effect” not “affect”. The difference is not a word game but an important way to think about database performance. Many things can affect performance. For example, if the system runs out of memory then starts swapping which causes high disk IO latency, that will negatively affect performance. But external factors like that notwithstanding (i.e. when hardware and MySQL are normal and stable), it’s important to understand that queries effect performance.
So far, I have written two tutorial blogs about MySQL InnoDB Cluster . Those blogs describe about the InnoDB Cluster configuration and how to integrate InnoDB Cluster with the MySQL router . You can get them through the below links .
- MySQL InnoDB Cluster Tutorial 1 ( Group Replication + MySQL Shell )
- MySQL InnoDB Cluster Tutorial 2 ( Integrating with MySQL router )
In this blog I am going to explain the following two things ,
- How to switch the cluster to ( single | multi ) primary mode without downtime ?
- How to make the specific node as the Primary member without …
In the many years we have used MySQL, we got accustomed to the fact that upgrades from MySQL 5.7.11 to 5.7.12 was a minor event. This meant that if something was going wrong, we could roll back the binaries and be happy again.
From MySQL 8, this is no longer true. Any upgrade, even minor, is seen as irreversible. (This is valid for Percona Server for MySQL as well.)
Say we have MySQL 8.0.17 and we upgrade to 8.0.18. In our MySQL log at the start, we will have this:
[System] [MY-010116] [Server] /opt/mysql_templates/mysql-8P/bin/mysqld (mysqld 8.0.18) starting as process 13242 … [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' started. … [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' completed. … [System] [MY-010931] [Server] /opt/mysql_templates/mysql-8P/bin/mysqld: …[Read more]
I am writing a tutorial on the MySQL Document Store for the sold
out (sorry) pre-FOSDEM MySQL days. For those who do not
write such exercise they are often a difficult task as you have a
limited time to convey information, need to provide vivid
examples, and create exercises that give a good idea of what the
topic is all about. And my personal preference is to write
once and use the tutorial at other events (please let me know
if you have such an event).
Indexing records is a well know performance step when creating
databases, SQL or NoSQL. And back in June of 2017 I wrote a
blog post on using createIndex() to index documents in the
MySQL Document Store. And as part of creating the tutorial I
referred to that blog post as a reference and was quite surprised
that it was not working.
What happened? Well back in 8.0.11 the function was revised and
it is no longer a series of chained calls but …
If you are thinking of using ProxySQL in our Percona XtraDB Cluster environment, I’ll explain how to use ProxySQL 2 for failover tasks.
How to Test
ProxySQL uses the “weight” column to define who is the WRITER node. For this example, I’ll use the following list of hostnames and IPs for references:
+-----------+----------------+ | node_name | ip | +-----------+----------------+ | pxc1 | 192.168.88.134 | | pxc2 | 192.168.88.125 | | pxc3 | 192.168.88.132 | +-----------+----------------+
My current WRITER node is the “pxc1” node, but how can I see who is the current WRITER? It’s easy, just run the following query:
proxysql> select hostgroup_id, comment, hostname, status, weight from runtime_mysql_servers;
This is the output: …
[Read more]