Showing entries 1 to 10 of 22074
10 Older Entries »
Displaying posts with tag: MySQL (reset)
Can Oracle Save MySQL?

I got quite a response to my article on whether Oracle is Killing MySQL, including a couple of great write-ups on The Register (1, 2)  on the topic.  There are a few questions in this discussion that I think are worth addressing.  AWS and other cloud vendors compete, without giving anything back, what else would […]

Resume Your Failed pt-online-schema-change Job

Starting from Percona Toolkit 3.6.0, you can resume pt-online-schema-change if it was interrupted. This blog describes the prerequisites and usage of the new –resume option. To restart the job, you need to know where it failed. This is why the first option you must use is –history. It instructs pt-online-schema-change to store its progress in […]

Sakila, Where Are You Going?

At Percona, we monitor our users’ needs and try to accommodate them. One aspect we monitor is the MySQL version distribution/utilization. Observing that, we identified a very interesting trend: the lack of migration from 5.7 to 8.x, or better yet, the need of many to remain on 5.7.  That observation has triggered several actions from […]

GCache and Record-Set Cache Encryption in Percona XtraDB Cluster – Part Two

Keeping Your Data Safe: An Introduction to Data-at-Rest Encryption in Percona XtraDB Cluster. In the first part of this blog post, we learned how to enable GCache and Record-Set cache encryption in Percona XtraDB Cluster. This part will explore the details of the implementation to understand what happens behind the scenes. How does it work […]

The curse of MySQL warnings

MySQL warnings are an anti-pattern when it comes to maintaining data integrity. When the information retrieved from a database does not match what was entered, and this is not identified immediately, this can be permanently lost.

MySQL by default for several decades until the most recent versions enabled you to insert incorrect data, or insert data that was then truncated, or other patterns that resulted in failed data integrity. Very few applications considered handling warnings as errors, and there is a generation of software products that have never informed the developers that warnings were occurring.

The most simplest example is:

CREATE SCHEMA IF NOT EXISTS warnings;
USE warnings;

CREATE TABLE short_name(
  id INT UNSIGNED NOT NULL AUTO_INCREMENT,
  name VARCHAR(20) NOT NULL,
  PRIMARY KEY(id)
);

INSERT INTO short_name (name) VALUES ('This name is too long and will get truncated');
ERROR 1406 (22001): Data too long for …
[Read more]
Is Oracle Finally Killing MySQL?

Some 15 years ago, when Oracle acquired Sun, and hence MySQL, there was a lot of talk on the internet over when Oracle was going to “Kill MySQL”.  Multiple theories were circled around, ranging from killing MySQL altogether, so there is less competition to proprietary Oracle, or just killing it as an open source project, […]

GCache and Record-Set Cache Encryption in Percona XtraDB Cluster – Part One

Keeping Your Data Safe: An Introduction to Data-at-Rest Encryption in Percona XtraDB Cluster. Data breaches are a major concern today. Whether you’re a business owner or value your privacy, the thought of your sensitive information being exposed is unsettling. Fortunately, data-at-rest encryption can help. Think of it as a sophisticated lock that scrambles your data, […]

Perl DBD MySQL for MySQL 8.0 and 8.4 LTS

Some years ago, I wrote an article on connecting to MySQL 8.0 using the default authentication plugin (caching_sha2_password) with Perl. I also provided Perl-DBD-MySQL packages for EL7.

Somebody recently left a comment as he was looking for a perl-DBD-MySQL driver compatible with the caching_sha2_password for Rocky Linux 8 (EL8 or OL8 compatible).

Therefore, I build two new packages supporting the latest perl-DBD-MySQL driver, version 5.005.

The difference is related to the version of libmysql they are linked to.

libmysql.so.21 for MySQL 8.0 and libmysql.so.24 for MySQL 8.4 LTS:

MySQL 8.0

$ rpm -qf …
[Read more]
Why MySQL Replication Is Fast

Replication being slow—replication lag—is a common complaint, but MySQL replication is actually really fast. Let’s run a controlled experiment and peek inside the Performance Schema binary logs to see why.

Why MySQL Replication Is Fast

Replication being slow—replication lag—is a common complaint, but MySQL replication is actually really fast. Let’s run a controlled experiment and peek inside the Performance Schema and binary logs to see why.

Showing entries 1 to 10 of 22074
10 Older Entries »