Ideas, releases, practical guides, and perspectives from the people building with MySQL.
Earlier last week I was working with Percona Binlog Server, Percona’s tool for archiving the MySQL binary log (binlog) outside of a traditional replica and exploring what it can do.…
The post How to setup and use Percona Binlog Server (PBS) first appeared on Change Is Inevitable.
Starting with Percona XtraDB Cluster (PXC) 8.0, replication traffic encryption is enabled by default. That said, it’s common to find clusters running without TLS that suddenly need it: a new compliance requirement, an audit finding, a network segment that is no longer considered trusted.
PXC has a variable for exactly that case, pxc-encrypt-cluster-traffic, which handles SSL encryption for inter-node traffic, including State Snapshot Transfer (SST), Incremental State Transfer (IST), and the group communication the nodes use for replication.
The variable is not dynamic, and turning it on normally costs a full cluster restart since the node that encrypts traffic listens on ssl:// while its peers are still on tcp://. If a node joins the cluster with TLS enabled while remaining nodes don’t, the restarting node fails to reach out to the other peers with the following error:
2026-09-02T02:16:02.359992Z 0 [Note] [MY-000000] …[Read more]
MySQL HeatWave telemetry is the built-in capability for exporting selected MySQL server logs to an observability destination. When telemetry is configured with OCI Log Analytics, it export MySQL log natively for search and analysis – supporting security investigations, database and operational errors troubleshooting, identification of costly SQL and performance bottlenecks, and centralized audit records for […]
Manage recurring maintenance windows, defer disruptive maintenance, and audit maintenance activity with a reusable Bash utility. MySQL HeatWave on Oracle Cloud Infrastructure gives administrators control over when scheduled maintenance can occur and, with maintenance-disabled windows, the ability to temporarily defer non-critical maintenance that would cause downtime. That flexibility is useful when a DB System supports […]
There are a few cryptography tasks that are common to many
backends. For example, you should store passwords such that a
database leak doesn't expose them, you should sign payloads so
the receiving side can verify them, you should keep a column's
data unreadable outside the database, and you should mint tokens
an attacker cannot guess. MySQL's built-in functions cover part
of that ground but fall short for many users. The
SHA2() function will hash a password, but nothing
salts it for you, so two people who pick the same password end up
with the same stored value. MySQL does not have a built-in HMAC
function. An HMAC is the keyed hash a receiver uses to tell a
real message from a forged one.
When a database doesn't solve a problem natively, the work invariably moves up into application code, where every service reimplements it just a little bit differently. This adds ongoing maintenance complexity.
The …
[Read more]When setting up a new database for an application, high availability (HA) is one of the main priorities. Let’s assume for this example that you chose to use a Percona XtraDB (PXC) cluster to host your database. But how does the application know which PXC node is healthy and can receive application traffic? Introducing a cluster of ProxySQLs can solve this problem, as ProxySQL will healthcheck the database nodes and route the application traffic to the healthy nodes. However, now the HA problem comes up again: how does the application know which ProxySQL host is healthy?
Putting “one more component” in front of your servers to make them highly available just shifts the problem up by one layer. From making the database HA, to making ProxySQL HA, to needing to make HAProxy HA and so on…
At some point, you may land on the common HA strategy, keepalived, but BGP ECMP is a powerful alternative worth considering.
What …
[Read more]
The alert fires at 06:37 and by the time anyone opens a laptop
the database is back. The application log holds a wall
of Lost connection to MySQL server during
query, uptime says 41 days, and the
error log records a clean shutdown: no crash, no signal, no
out-of-memory kill. The next morning it happens at 06:12, and the
morning after that not at all.
On a default Ubuntu or Debian
server, unattended-upgrades installs
security updates on a daily systemd timer, and when one touches
MySQL, dpkg stops mysqld, upgrades the data
directory to match the new binary, and starts it again while the
machine stays up. Nothing rebooted. The database was replaced
underneath a host that never stopped running.
That is deliberate, and the part nobody signed up for is that “a service” includes the database. We put a client in front of MySQL on an Amazon Elastic …
[Read more]Your application code branches in seconds. Your database still gets copied, shared, and fought over. Here is how database branching closes that gap, where it breaks down, and what has to sit around it before it makes releases safer.
The post Database Branching Explained: How It Works and When to Use It appeared first on Devart Blog.
Twitter login with Node breaks every few years because the pieces move under it. I rebuilt this app on the current releases and fixed each place where the old code stops working, so you can follow it step by step and finish with a working sign-in. Live Demo Download Code Pick the right X auth […]
As we have discussed through the new MySQL Community Engagement initiative, we are sharing metrics that highlight how the community contributes to MySQL. These measures help us understand the growth of community participation, recognize the people helping improve the product, and identify where we can continue to strengthen the contributor experience. The MySQL community delivered […]