本文讨论了在Kubernetes环境中使用MySQL组复制时的高可用性问题，特别关注内存管理和流控机制。文章指出，当Pod内存使用超过限制时，Kubernetes会触发OOMKill，导致服务中断。为确保高可用性，建议在流控配置中采取更严格的措施，以防止内存增长过快导致数据库崩溃。

On May 26, The MySQL Community Team at Oracle welcomed MySQL contributors, customers, partners, and community members to the MySQL Contributor Summit at the Oracle Redwood Shores campus, with...

The MySQL team has been working hard to foster innovation, strengthen collaboration with our community, support meaningful contributions, and grow the broader MySQL ecosystem through greater...

MySQL 9.7 LTS is here, establishing the new MySQL 9.7.x Long-Term Support release line. For organizations running MySQL today, this is the right time to evaluate upgrade plans and move toward a...

Modern applications often pass JSON back and forth with the database server. With MySQL, we have had great JSON support, but working with relational data as JSON usually meant generating documents...

A few months ago, I was asking myself how to insert in two tables in a single round-trip to the database.  I wanted to do that to optimize a process.  My optimization involved splitting...

One of the best things about MySQL has always been its community. Whether you’re building applications, running production databases, contributing code, creating tools, writing documentation,...

When we introduced MySQL Studio, the goal was to bring the common parts of database development and analysis into one OCI workspace: SQL authoring, schema exploration, results visualization, and...

The MySQL Community team will be active across conferences, user group meetups, open source events, and regional community activities during the summer months. Whether you would like to hear about...

本文介绍了六个步骤用于排查MySQL性能问题：记录基线数据以确认性能变化、实时监控查询状态、检查InnoDB内部状态、定位慢查询并分析日志、检查配置参数的合理性，以及通过压测验证改动效果。这些步骤能有效减少错误，避免盲目修改。

Modern applications generate and consume enormous amounts of semi-structured data. User profiles, product catalogs, IoT telemetry, application events, AI prompts, and content metadata rarely fit...

PostgreSQL的HeapTable与MySQL的InnoDB IOT在处理大查询时机制不同。InnoDB使用持久游标保存查询位置，允许释放页面锁，减少修改冲突；而PostgreSQL通过Pin机制确保记录位置不变，避免频繁修改。两者在更新机制和逻辑复杂度上各有优势，PostgreSQL在读取时实现零拷贝，但在清理时面临负担。

Every MySQL ADO.NET provider looks reliable during development. The real differences appear later, when async performance breaks under load, licensing becomes a problem, or integrations with EF...

在选择适合Kubernetes的PostgreSQL操作员时，需评估不同开源解决方案的质量和特性，以满足特定需求。并非所有开源项目都具备相同的可靠性和支持。