# MySQL Published articles for MySQL. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator DevFeed: [Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator]() Original publisher: [Read original article]() Author: Anil Joshi Published: 2026-09-17T06:43:32Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [Replication](), [export](), [Percona Server for MySQL](), [configuration](), [Server](), [Kubernetes](), [Database]() Tags: [cloud](), [configuration](), [database-trends](), [featured](), [innodb-clusterset](), [insight-for-dbas](), [kubernetes](), [kubernetes-operators](), [mysql](), [mysql-group-replication](), [mysql-high-availability](), [mysql-replication](), [open-source](), [operator](), [percona-kubernetes-operators](), [percona-operator-for-mysql](), [percona-server-for-mysql](), [percona-software](), [replication](), [uncategorized](), [yaml]() ### AI overview This tutorial explains how to configure cross-site replication between two Percona Operator for MySQL clusters to create a ClusterSet environment for disaster recovery and switchover between data-center and disaster-recovery members. It covers deploying the clusters, retrieving endpoints and cluster names, transferring credentials, and initializing the DR cluster. ### Source excerpt A while ago, we discussed the cross-site replication feature of the Percona PXC operator. Recently, a similar cross-site replication feature was introduced in the Percona (PS MySQL) operator v1.2.0, a topology based on Group Replication/InnoDB Cluster. In this blog post, we will explore how to add a DR Cluster to an existing DC Cluster to ... Continued The post Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator appeared first on Percona. ## Too many GCache Page Files in MySQL Data Directory DevFeed: [Too many GCache Page Files in MySQL Data Directory]() Original publisher: [Read original article]() Author: Kedar Vaijanapurkar Published: 2026-09-17T05:29:14Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [XtraDB Cluster (PXC)](), [Replication](), [Transactions](), [MySQL]() Tags: [cluster](), [database-administration](), [disk-space](), [galera](), [galera-replication](), [gcache](), [gcache-freeze-purge-at-seqno](), [gcache-keep-pages-count](), [gcache-page](), [gcache-page-files](), [gcache-purge](), [gcache-troubleshooting](), [mysql](), [mysql-disk-space](), [mysql-troubleshooting](), [percona-xtradb-cluster](), [pxc](), [replication](), [xtradb-cluster-pxc]() ### AI overview An investigation into thousands of GCache page files accumulating in a Percona XtraDB Cluster data directory. The article explains how frozen GCache purging caused disk growth, links the behavior to a cluster partition, and describes reproducing it by setting gcache.freeze_purge_at_seqno and generating workload. ### Source excerpt Learn why PXC accumulates thousands of gcache.page.* files, how frozen GCache purging causes disk growth, and how to safely recover and rejoin using IST. The post Too many GCache Page Files in MySQL Data Directory appeared first on Percona. ## Keycloak 26.7.4 released DevFeed: [Keycloak 26.7.4 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Security](), [Quarkus](), [MariaDB](), [MySQL](), [saml]() Tags: [cve](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [mariadb](), [mysql](), [openid-connect](), [quarkus](), [release](), [saml](), [security](), [sso]() ### AI overview Keycloak 26.7.4 was released on September 16, 2026. The release includes security fixes for several CVEs, an upgrade to Quarkus 3.33.3.2, and fixes for performance, testing, documentation, administration, and UI issues. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Security fixes #52834 [CVE-2026-90997] Default MySQL/MariaDB row counts make stateless replay gates accept reused artifacts #52835 [CVE-2026-79651] Keycloak Unauthenticated Denial of Service via Unbounded Locale Caching #52836 [CVE-2026-74909] Incomplete fix: percent-encoded semicolon bypasses matrix parameter stripping in PathMatcher #52837 [CVE-2026-19607] Username Takeover Leading to Account Lockout #52838 [CVE-2026-17526] Privilege escalation: the "impersonation" role can impersonate a realm administrator #52839 [CVE-2026-18212] SAML Redirect DEFLATE helpers leak native zlib state Enhancements #52354 Upgrade to Quarkus 3.33.3.2 dist/quarkus Bugs #49635 Performance issue with 26.6.2 dist/quarkus #51102 Flaky test: org.keycloak.testsuite.oauth.AccessTokenTest#accessTokenRequest ci #52015 New links errors for https://quarkus.io/guides docs #52172 Cached `RealmAdapter.isUserManagedAccessAllowed()` returns `isEnabled()` infinispan #52173 `realm_client` is computed into a client's attributes and then persisted on save admin/api #52233 Oracle 19 full client OCI driver crashes on startup since 26.6.0 -- SQLFeatureNotSupportedException on setNetworkTimeout dist/quarkus #52241 Clicking on a sub group in the admin console throws an exception admin/ui #52283 Flaky test SessionRestServiceTest.testGetDevicesSessions testsuite #52430 Flaky test: userprofile.spec.ts fails with timeout on "no-users-found-empty-action" in serial suite testsuite ## Announcing Fedora Linux 45 Beta DevFeed: [Announcing Fedora Linux 45 Beta]() Original publisher: [Read original article]() Author: Aoife Moloney Published: 2026-09-15T14:05:00Z Content type: release Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Linux](), [dnf](), [podman](), [pandas](), [Python](), [gcc](), [Go Language](), [MariaDB](), [MySQL](), [Filesystems]() Tags: [2026](), [dnf](), [fedora-project-community](), [filesystems](), [gcc](), [go](), [linux](), [mysql](), [pandas](), [partitioning](), [podman](), [pre-release](), [python](), [release](), [toolchains]() ### AI overview Fedora Linux 45 Beta is available for download or upgrade on September 15, 2026. The release includes changes to the kernel console, package signature verification, desktop secret management, software versions, Atomic Desktop image builds, Fedora CoreOS swap support, Anaconda installation flows, and Stratis filesystem partitioning. ### Source excerpt Fedora Linux 45 Beta is here! On Tuesday, 15 September 2026 you can download or upgrade your systems from your usual spots to start enjoying what F45 has to offer early. How to get the beta release You can download F45 Beta, or our pre-release edition versions, from any of the following places: You can [...] ## Performance improvements in Percona Server 8.4.11-11 DevFeed: [Performance improvements in Percona Server 8.4.11-11]() Original publisher: [Read original article]() Author: Bogdan Degtyariov Published: 2026-09-15T11:52:54Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [Percona Server for MySQL](), [Percona](), [MySQL](), [Cache](), [Scalability](), [Database]() Tags: [benchmark](), [benchmarks](), [cache](), [io](), [mysql](), [percona](), [percona-server-for-mysql](), [performance](), [scalability]() ### AI overview This article describes performance and scalability improvements in Percona Server for MySQL 8.4.11-11, focusing on changes to the InnoDB buffer pool and page flushing. It explains how narrowing mutex coverage and using finer-grained latching allows physical reads to proceed more in parallel, particularly for read-heavy, I/O-bound workloads. ### Source excerpt Focusing on Percona Server 8.4.11-11 My previous post (Performance Progression of Percona Server for MySQL 8.4) did a brief review of the performance changes in Percona Server for MySQL 8.4 released in 2026. I recommend reading it first to better understand the material in this post. Version 8.4.11-11 includes patches that deliver significant improvements in ... Continued The post Performance improvements in Percona Server 8.4.11-11 appeared first on Percona. ## Intelligence is yours. Let's keep it that way. DevFeed: [Intelligence is yours. Let's keep it that way.]() Original publisher: [Read original article]() Author: Paddy Srinivasan Published: 2026-09-14T21:11:13Z Content type: opinion Language: en Sources: [DigitalOcean]() Topics: [Open Source](), [Software](), [PostgreSQL](), [React](), [GitHub]() Tags: [agents](), [competition](), [github](), [infrastructure](), [intellectual-property](), [kubernetes](), [models](), [mysql](), [news](), [open-source](), [opencode](), [postgresql](), [react]() ### AI overview The article argues that founders should retain ownership and control of their companies' intelligence rather than depend on a single intelligence provider. It advocates an Open Intelligence movement built from open-source models, agents, harnesses, data technologies, and infrastructure, drawing comparisons with the adoption of Linux, PostgreSQL, MySQL, Kubernetes, and other open technologies. ### Source excerpt Intelligence was yours. A founder's intellectual property, business logic, differentiation, their intelligence, was once theirs alone. You built it, you owned it, and no tools/platform vendor stood between you and your customers. This is no longer clear. It is starting to look like it is "theirs." Intelligence can now be manufactured: the models, the agents and the harnesses that drive them, and the compute they run on. Providers who own all these can produce the application, and the differentiation, in every industry. That power runs the risk of becoming increasingly concentrated in a handful of companies. The race for the application layer is not about interfaces or go-to-market; it is a fight over who owns the intelligence layer itself. We have seen this before but we must act before its too late. Linux started behind Unix and Windows and now runs most of the world's servers. PostgreSQL and MySQL started behind Oracle and now underpin most new software. Kubernetes arrived after proprietary orchestrators and made them irrelevant. Each began less capable and won anyway: builders could see inside it, run it anywhere, and never had to ask permission. The same is happening now. Open weight models have repeatedly reached the frontier this past year. Open harnesses like OpenCode have grown to tens of trillions of tokens a day. Hermes reached more than 200,000 GitHub stars in five months, a milestone that took React a decade to achieve. Along with the near total adoption of open source data technologies, this collection of open technologies power an Open Intelligence movement. Open Intelligence restores the order. It returns to founders ownership of what makes their companies theirs. Founders should be free to build without tying their future to a single intelligence provider: their choice of agents, harnesses, data technologies, models, and infrastructure, with open source transparency, control, and competition keeping every layer honest. The stakes go beyond business. ## Linux server performance: Is disk I/O slowing your application? DevFeed: [Linux server performance: Is disk I/O slowing your application?]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-12T16:11:54Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [IO](), [Server](), [Command-line interface](), [Processes](), [NVMe]() Tags: [blog](), [command-line](), [cpu](), [linux](), [load](), [mysql](), [nvme](), [performance](), [processes](), [request](), [server](), [ssd](), [storage](), [sysadmins](), [terminal]() ### AI overview This tutorial explains how disk I/O bottlenecks can cause high Linux load averages even when CPU usage is low. It shows how to use top, atop, and iotop on a LEMP web server, including per-core I/O wait measurements, to identify storage-related application slowdowns. ### Source excerpt If your Linux server is bogged down by disk I/O, your first step may often be to use the top command in the terminal to check load averages. Continue reading... ## Introducing Neki DevFeed: [Introducing Neki]() Original publisher: [Read original article]() Author: Nick Van Wiggeren Published: 2026-09-10T12:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [Database](), [MySQL]() Tags: [database](), [mysql](), [neki](), [platform](), [postgres](), [product](), [routing](), [scale](), [workflow]() ### AI overview PlanetScale announces Neki in platform preview, a sharded Postgres offering designed to scale a database across multiple machines while retaining Postgres compatibility. ### Source excerpt Neki, sharded Postgres by PlanetScale, is now available in platform preview. ## GitHub availability report: August 2026 DevFeed: [GitHub availability report: August 2026]() Original publisher: [Read original article]() Author: Jakub Oleksy Published: 2026-09-10T02:05:17Z Content type: article Language: en Sources: [GitHub Engineering]() Topics: [GitHub](), [site-reliability-engineering](), [migration](), [MySQL](), [GitHub Actions]() Tags: [availability](), [azure](), [company-news](), [database](), [github](), [github-actions](), [github-availability-report](), [migration](), [monitoring](), [mysql](), [news-insights](), [outage](), [performance](), [production]() ### AI overview GitHub reports five August incidents with degraded service performance and describes capacity, resiliency, database, Azure migration, and GitHub Actions improvements. ### Source excerpt In August, we experienced five incidents that resulted in degraded performance across GitHub services. The post GitHub availability report: August 2026 appeared first on The GitHub Blog. ## PostgreSQL Migrator 1.0 : first stable release DevFeed: [PostgreSQL Migrator 1.0 : first stable release]() Original publisher: [Read original article]() Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [migration](), [Databases](), [releases](), [MySQL](), [Oracle Database](), [ci]() Tags: [ci](), [migration](), [mysql](), [open-source](), [oracle](), [postgresql](), [release]() ### AI overview PostgreSQL Migrator 1.0 is the first stable release of an open-source tool for migrating Oracle, MySQL, and MariaDB databases to PostgreSQL. It supports full inspection and limited conversion and migration for selected database objects, with compatibility promised across 1.x releases. ### Source excerpt Paris, 7th september 2026. The Dalibo team is pleased to announce the release of PostgreSQL Migrator 1.0 stable, a free and open-source tool designed to help migrate databases from Oracle and MySQL/MariaDB to PostgreSQL. Key features Easy installation: pure Go binary with zero proprietary dependencies. Fast, offline inspection: Extract the full source catalog once, then iterate on conversion offline. Complexity scoring: Quickly assess and compare the difficulty of migration projects. Interactive web UI: Browse both the original and converted catalogs, search objects, and identify migration blockers. Schema and data conversion: Converts datatype and SQL expression, convert column to boolean. Code analysis and transpilation: Transpiles and analyzes SQL, PL/SQL and routines with the companion transqlate tool. High-performance data copy: Streamed bulk COPY to PostgreSQL (or to files / pipes), with low memory usage and significantly higher throughput than traditional tools in our tests. Hackable & configurable: Reliable JSON catalog data, TOML configuration, and templating for fine-tuning. Supported features PostgreSQL Migrator supports migrating from Oracle Database 11g to 26ai, MySQL 8.4+ and MariaDB 10+ to PostgreSQL 16 up to 19. Version 1.0 has full inspection including jobs, system triggers, etc. However, conversion and migration is limited to role, schema, sequences, table, virtual columns, constraints and indexes. The documentation describes implemented and planned features including views, procedural objects, SQL Server and more. Stability We have built a demanding CI pipeline including end-to-end tests based on Oracle Free container and cypress. This effectively prevents regression and ensure quality. After one year of beta and rc, PostgreSQL Migrator is stable. We'll ensure configuration, CLI and project compatibility for all 1.x releases. License and availability PostgreSQL Migrator is released under the PostgreSQL License. Documentation: https://postgresql-mi ## Loading Parquet data into MySQL with ClickHouse DevFeed: [Loading Parquet data into MySQL with ClickHouse]() Original publisher: [Read original article]() Author: Mark Needham Published: 2026-09-10T00:00:00Z Content type: tutorial Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [MySQL](), [parquet](), [Databases](), [Amazon S3]() Tags: [clickhouse](), [mysql](), [parquet](), [s3](), [sql]() ### AI overview A tutorial on using ClickHouse to load Parquet data into MySQL and query MySQL through ClickHouse table functions. ### Source excerpt Use ClickHouse to load Parquet files into MySQL, explore remote data, and run MySQL queries with table functions and named collections. ## Enabling TLS in PXC without Downtime DevFeed: [Enabling TLS in PXC without Downtime]() Original publisher: [Read original article]() Author: Juan Arruti Published: 2026-09-09T23:32:15Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [TLS (Transport Layer Security)](), [Replication](), [Security](), [Network](), [openssl]() Tags: [galera](), [high-availability](), [insight-for-dbas](), [mysql](), [open-source](), [percona](), [pxc](), [replication](), [security](), [ssl](), [tls](), [tls-handshake](), [uncategorized](), [xtradb-cluster-pxc]() ### AI overview This tutorial explains how to enable TLS for replication traffic in Percona XtraDB Cluster without a full cluster restart. Using Galera's socket.dynamic option, operators can perform two rolling restarts: first allowing encrypted and plaintext connections, then enforcing TLS-only communication. ### Source excerpt 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 ... Continued The post Enabling TLS in PXC without Downtime appeared first on Percona. ## Troubleshoot AWS Advanced JDBC Wrapper configuration for Aurora Global Database write forwarding DevFeed: [Troubleshoot AWS Advanced JDBC Wrapper configuration for Aurora Global Database write forwarding]() Original publisher: [Read original article]() Author: Hema Saminathan Published: 2026-09-03T16:26:20Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [configuration](), [Database](), [MySQL](), [Latency]() Tags: [advanced-300](), [amazon-aurora](), [aws](), [drivers](), [global](), [latency](), [mysql](), [postgresql](), [technical-how-to]() ### AI overview A configuration troubleshooting guide for the AWS Advanced JDBC Wrapper with Aurora Global Database write forwarding. It explains Region-specific settings for primary and secondary Regions, including MySQL-specific write-forwarding behavior. ### Source excerpt Configuring the AWS Advanced JDBC Wrapper for Amazon Aurora Global Database with write forwarding requires Region-specific settings, and misconfiguration causes latency spikes and connection failures. This post walks through the correct dialect, plugins, host patterns, and write forwarding settings for the primary and secondary Regions. ## JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled DevFeed: [JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Databases](), [Latency](), [client](), [Code]() Tags: [batching](), [bulk-load](), [client](), [cost](), [database](), [database-performance](), [durability](), [jdbc](), [latency](), [mysql](), [postgresql](), [server](), [sql]() ### AI overview For small database writes, network round trips and transaction overhead can dominate the actual insert work. The article explains that JDBC batching may accept rows into a client-side batch while still sending separate statements unless driver-side statement rewriting is enabled, and that autocommit adds a transaction and durability barrier per row. ### Source excerpt For small writes the per-statement overhead dominates the actual work, so throughput is set by round trips rather than by the database. JDBC batching is the usual fix and it silently does nothing on the wire unless the driver is told to rewrite the statements, so addBatch can look correct while still issuing one round trip per row. Autocommit compounds it by turning every row into its own transaction and its own durability barrier, which is the difference between one fsync and a hundred thousand. ## MySQL CDC connector for ClickPipes is now Generally Available DevFeed: [MySQL CDC connector for ClickPipes is now Generally Available]() Original publisher: [Read original article]() Author: Marta Paes Published: 2026-09-02T14:03:04Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [MySQL](), [Infrastructure as code](), [Terraform]() Tags: [analytics](), [api](), [clickhouse](), [cloud](), [data](), [infrastructure-as-code](), [mysql](), [observability](), [release](), [terraform]() ### AI overview ClickHouse announces general availability of its MySQL CDC connector for ClickPipes, which replicates MySQL and MariaDB data into ClickHouse Cloud. The release adds automatic parallel snapshotting, reliability and observability improvements, and configuration through the Cloud API and Terraform. ### Source excerpt Replicate MySQL and MariaDB data into ClickHouse Cloud with the generally available MySQL CDC connector, featuring faster parallel snapshots, safer production defaults, improved observability, and infrastructure-as-code support. ## OpenID Connect Authentication for MySQL, Now Fully Open Source DevFeed: [OpenID Connect Authentication for MySQL, Now Fully Open Source]() Original publisher: [Read original article]() Author: Michał Jankowski Published: 2026-09-02T08:56:26Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [MySQL](), [OpenID connect (OIDC)](), [Authentication](), [JSON Web Tokens](), [OAuth](), [Open Source]() Tags: [authentication](), [jwks](), [jwt](), [mysql](), [oauth](), [oauth-2-0](), [oidc](), [open-source](), [openid-connect](), [percona](), [percona-server-for-mysql](), [percona-software](), [security]() ### AI overview Percona Server for MySQL includes an open-source OpenID Connect authentication plugin for specified 8.4 and 9.7 releases. The article explains how it authenticates users through standards-compliant identity providers and describes capabilities beyond the MySQL Enterprise plugin, including JWKS signing-key synchronization, group-to-role mapping, and proxy-user support. ### Source excerpt Percona Server for MySQL now ships with a fully open source OpenID Connect (OIDC) authentication plugin, available starting with Percona Server for MySQL 8.4.11-11 and 9.7.2-2 (not yet released as of this writing). It allows a MySQL account to authenticate against any standards-compliant Identity Provider (IdP) instead of relying on a locally stored password, closing ... Continued The post OpenID Connect Authentication for MySQL, Now Fully Open Source appeared first on Percona. ## How INTEGER and INT Produced Different Schemas in Debezium DevFeed: [How INTEGER and INT Produced Different Schemas in Debezium]() Original publisher: [Read original article]() Author: Prathit Malik Published: 2026-09-02T07:02:02Z Content type: article Language: en Sources: [Grofers]() Topics: [MySQL](), [migration](), [Streaming](), [Kafka](), [SQL](), [Databases]() Tags: [big-data](), [blinkit](), [change](), [database](), [debezium](), [jdbc](), [kafka](), [migration](), [mysql](), [open-source](), [schema](), [sql](), [streaming]() ### AI overview This article investigates a Debezium CDC pipeline failure caused by MySQL INT and INTEGER synonyms being treated as different types. The resulting schema mismatch produced an Integer where a downstream consumer expected a Long, causing a ClassCastException on every batch. It explains how streaming and snapshot schema handling differ and how routine migrations exposed the problem. ### Source excerpt A Debezium investigation: how MySQL synonyms INT and INTEGER were treated as different types. One of our CDC pipelines started failing with a ClassCastException on every batch. java.lang.ClassCastException: class java.lang.Integer cannot be cast to class java.lang.Long The pipeline was producing an Integer, but the downstream consumer expected a Long. Every run failed in the same way, which pointed us toward a schema mismatch rather than an issue with individual records. Background: how CDC works To see why a mismatch like that can hide for years, it helps to know how CDC actually works. Most companies replicate their transactional database (MySQL, Postgres, something similar) into a separate data lake for analytics, rather than querying the source directly, and Change Data Capture (CDC) is what keeps that copy in sync: it tails the database's transaction log and replays every insert, update, and delete downstream. Debezium is the most widely used open-source CDC tool for MySQL, and it builds a table's schema in one of two ways that are supposed to agree but do not always. Streaming mode: the first time it sees a CREATE TABLE or ALTER TABLE in the binlog, it parses the raw SQL text and writes the result to its own internal Kafka topic, database.history.kafka.topic. Every restart after that rebuilds the in-memory schema by replaying that topic, not by re-reading the binlog. Snapshot mode: reads the table definition fresh through MySQL's JDBC metadata interface, which normalizes types, every time it runs. Schema Registry sits downstream of both: each connector writes whatever schema it built into the registry, but neither connector reads its own schema back from it. Keep that in mind; it matters later. The trigger: a routine migration With that in mind, here's what actually happened to us. Rewind two years: one of our upstream service teams added a few columns to a source table as part of a standard schema change. ALTER TABLE ADD COLUMN length double NU ## Announcing native MySQL databases: Bring your MySQL workloads to Appwrite DevFeed: [Announcing native MySQL databases: Bring your MySQL workloads to Appwrite]() Original publisher: [Read original article]() Author: Jake Barnby Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [MySQL](), [Databases](), [Provisioning](), [Availability](), [Replication](), [autoscaling](), [TLS (Transport Layer Security)]() Tags: [announcements](), [autoscaling](), [availability](), [database](), [databases](), [mysql](), [provisioning](), [replication](), [tls]() ### AI overview Appwrite announces native managed MySQL databases that can run inside the same project as an application's existing backend. The service supports MySQL 8.4 and 8.0, standard drivers and ORMs, TLS, backups and point-in-time recovery, replicas with automatic failover, database branches, scaling, and connection pooling. ### Source excerpt Provision a managed MySQL 8.4 instance inside your Appwrite project and keep using the drivers, ORMs, and tools your applications already depend on. ## Native databases vs Appwrite databases: which one should you pick? DevFeed: [Native databases vs Appwrite databases: which one should you pick?]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Databases](), [MySQL](), [PostgreSQL](), [SDKs]() Tags: [api](), [backend](), [comparisons](), [databases](), [guide](), [mysql](), [orm](), [postgresql](), [realtime](), [transactions]() ### AI overview This guide compares Appwrite's managed TablesDB, DocumentsDB, and VectorsDB with native PostgreSQL and MySQL databases. It explains the trade-off between Appwrite's SDK-based permissions, realtime events, functions, and other platform features and the direct SQL access available through native database drivers or ORMs. ### Source excerpt Appwrite offers two kinds of databases. This guide explains how TablesDB, DocumentsDB, and VectorsDB differ from native PostgreSQL and MySQL, and how to choose between them for your project. ## How one connection kills a database DevFeed: [How one connection kills a database]() Original publisher: [Read original article]() Author: Simeon Griggs Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [debugging](), [migration](), [dashboards](), [vitess]() Tags: [app](), [cli](), [database](), [debugging](), [errors](), [exception](), [github](), [management](), [migration](), [mysql](), [postgres](), [product](), [transactions](), [vitess]() ### AI overview The article explains how an unclosed database transaction can block a migration and queue later queries, causing downtime. It discusses diagnosing live MySQL and Postgres connections and preventing stuck Postgres transactions with a timeout. ### Source excerpt Unblock stuck connections with live connection management in the PlanetScale CLI and dashboard ## Announcing Appwrite 2.0: a new foundation for your apps DevFeed: [Announcing Appwrite 2.0: a new foundation for your apps]() Original publisher: [Read original article]() Author: Eldad Fux Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Databases](), [Amazon S3](), [OAuth](), [Firewall](), [MySQL](), [PostgreSQL]() Tags: [feature](), [firewall](), [mysql](), [oauth](), [postgresql](), [products](), [release](), [s3]() ### AI overview Appwrite 2.0 is a major platform release with a new engine, rebuilt Console, relational, schemaless, and vector data support, native PostgreSQL and MySQL engines, S3-addressable storage, OAuth 2.1 and OpenID Connect support, and organization-level Domains and Firewall. ### Source excerpt Appwrite 2.0 brings a new engine, a rebuilt Console, five database types, an S3 API, an OAuth 2.1 server, and organization-level Domains and Firewall. ## 【kube-apiserver】选型收束与开放问题：排除树、Kine 与 events 分集群 DevFeed: [【kube-apiserver】选型收束与开放问题：排除树、Kine 与 events 分集群]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [Caching](), [etcd](), [SQL](), [MySQL](), [PostgreSQL](), [SQLite](), [Raft]() Tags: [apiserver](), [churn](), [distributed](), [errcompacted](), [etcd](), [events](), [exclusion-tree](), [kine](), [kubernetes](), [mysql](), [open-questions](), [postgresql](), [quota](), [raft](), [selection](), [sql](), [sqlite](), [storage](), [ttl](), [v1-30-3](), [watch-cache]() ### AI overview This concluding article presents a mechanism-based decision tree for diagnosing Kubernetes control-plane issues across kube-apiserver and etcd layers. It explains Kine's differing Watch semantics when using SQLite, PostgreSQL, or MySQL backends, discusses routing Kubernetes Events to a separate etcd cluster, and identifies open questions around watch-cache SLOs, compaction, linear reads, and Lease fencing. ### Source excerpt 用机制排除树收束何时查 apiserver 轴、何时穿透 etcd 轴、何时两轴联查；回收 etcd/13 写下的 apiserver 停损线；Kine SQL backend 的 Watch 语义差与 Jepsen 覆盖空白；events --etcd-servers-overrides 分集群运维；列出 watch cache SLO 联合模型、线性读期望与 Lease+fencing 全链路三个开放问题；以 ADR 语言关闭系列边界。 ## Performance Progression of Percona Server for MySQL 8.4 DevFeed: [Performance Progression of Percona Server for MySQL 8.4]() Original publisher: [Read original article]() Author: Bogdan Degtyariov Published: 2026-08-27T13:07:20Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [MySQL](), [benchmarking](), [Benchmark](), [Scalability](), [configuration](), [cpu](), [Hardware]() Tags: [2026](), [benchmark](), [benchmarking](), [benchmarks](), [concurrency](), [configuration](), [cpu](), [data](), [database](), [hardware](), [intel](), [latency](), [load](), [measurement](), [mysql](), [percona](), [percona-server-for-mysql](), [performance](), [processors](), [run]() ### AI overview This article investigates read/write performance changes across Percona Server for MySQL 8.4 versions released in 2026. It describes benchmark scope, database and buffer-size combinations, configuration, and CPU-frequency controls, while excluding features, security patches, latency percentiles, and resource-utilization measurements. ### Source excerpt 1. Purpose and scope This performance investigation aims to look into the read/write performance of Percona Server for MySQL 8.4 and how it changed between versions released in 2026: 8.4.8-8 released on 12 March 2026 8.4.10-10 released on 30 June 2026 8.4.11-11 released on 20 August 2026 We want to see if there are improvements ... Continued The post Performance Progression of Percona Server for MySQL 8.4 appeared first on Percona. ## ADD COLUMN is not always free, and the lock queue is what takes you down DevFeed: [ADD COLUMN is not always free, and the lock queue is what takes you down]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [PostgreSQL](), [incident](), [Query (disambiguation)](), [migration](), [MySQL]() Tags: [ddl](), [incident](), [locking](), [migration](), [migrations](), [mysql](), [postgresql](), [query](), [queues](), [schema-design](), [timeout]() ### AI overview Adding a nullable column can cause an outage even when the schema change itself is nearly instantaneous. In PostgreSQL, ALTER TABLE may wait for a long-running query, and subsequent queries can queue behind the waiting lock request. Setting a short lock_timeout and retrying can prevent the migration from taking down the table. ### Source excerpt Modern PostgreSQL adds a column with a default as a metadata change, so the table is never rewritten and the migration itself is instant. The outage comes from lock acquisition instead: ALTER TABLE needs an ACCESS EXCLUSIVE lock, and while it waits behind one long-running query, every subsequent query queues behind the waiting ALTER because the lock queue is ordered. Setting lock_timeout to a couple of seconds and retrying converts that from an outage into a no-op. [Next page]()